Hey folks,

We have a mapping that has a sequenceGenerator for creating the primary key. Alas as part of some new business we now need to be able
provide a primary key or not to the object. Alas when we provide a primary key hibernate thinks that the object has already been saved and doesn't
attempt to persist the object. Is there anyway we can override the behaviour that if the primary key is not null then hibernate doesn't save it
automatically?

thanks,
Mark.

Hi!

Did you try this:

or

?

You can also look into Interceptor.isUnsaved()

Regards,
David

Hey Xerces*,

Thanks for the reply.
yeah I'm looking at it now. I'm using the <version> tag and have added a column to my table.

I was worried that unsaved-value="any" would mean that the object would always be regarded as new?

unsaved-value="undefined" kinda implies to me that it will only attempt the save when the id is null. My object can have a null id and also have them assigned within the process without retrieving the value from the database, so the latter objects won't be saved.

What do ye think?

thanks,
Mark.