On my entities I have the id generated using the uuid generator:
@Id @GeneratedValue(generator="system-uuid")
@GenericGenerator(name="system-uuid",strategy="uuid")

This allows me to have id's guaranteed to be unique across environments (dev/stage/prod). However, I also want the ability to move my data across environments and still maintaining id's.

The problem I have is that if I migrate an object which has the id set and use the session.save(), then hibernate insists on using the generator, eventhough my primary key has a perfectly valid value.

Is there any way to turn of this behaviour?

Thanks in advance

I am wondering if you could extend this class, modify id annotation to assigned and in those scenarios use the extending class. I am not really sure if this works.


Farzad-

Thanks for the input. Perhaps its possible, but that will require me having two classes for each of my hibernated classes, which will quite bothersome in the long run.

Another hack I thought of was to have a helper class that used simple JDBC to create a row with the new id and then updating that id through Hibernate, but again, definately not a preferred approach if Hibernate could help in some way.

I was hoping there were some options one could put on the generator.