Assigned identifiers and Interceptor.isUnsaved()

unkyaku · **Joined:** Wed Oct 01, 2003 11:01 pm **Posts:** 23

According to section 5.1.4.5 of the reference manual,

Quote:

Due to its inherent nature, entities that use this [assigned] generator cannot be saved via the Session's saveOrUpdate() method. Instead you have to explicitly specify to Hibernate if the object should be saved or updated by calling either the save() or update() method of the Session.

Can I get around this restriction if I have an Interceptor that watches for these objects and returns the correct value in Interceptor.isUnsaved()?

Thanks.

christian · **Posted:** Tue May 11, 2004 2:53 am

Yes, you can also set an unsaved-value on the <version> or <timestamp> property.

unkyaku · **Joined:** Wed Oct 01, 2003 11:01 pm **Posts:** 23

christian wrote:

Yes, you can also set an unsaved-value on the <version> or <timestamp> property.

Christian, when using unsaved-value in <version>, is it necessary to set unsaved-value="none" in <id> since it defaults to null?

Thanks.

christian · **Posted:** Wed May 12, 2004 4:01 am

The unsaved <version> has precedence.