That is exactly what I was looking for.
Thanks again for a great tool.
Regards,
John
-Original Message-
From: Gavin King [mailto:[EMAIL PROTECTED]
Sent: Saturday, October 18, 2003 6:06 AM
To: Urberg, John
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Hibernate] Saving Collections fro
You need to upgrade to Hibernate 2.1, and understand the
select-before-update mapping
attribute.
Urberg, John wrote:
Hibernate also seems to always assume objects from different sessions are
dirty. (I'm using saveOrUpdate() in 1.2.5. Maybe this has changed in 2.*?)
Anyway, I need to work aroun
MAIL PROTECTED]
Sent: Thursday, October 16, 2003 3:12 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [Hibernate] Saving Collections from Multiple Sessions
Hibernate also seems to always assume objects from different sessions are
dirty. (I'm using saveOrUpdate() in 1.2.5. Maybe this
Hibernate also seems to always assume objects from different sessions are
dirty. (I'm using saveOrUpdate() in 1.2.5. Maybe this has changed in 2.*?)
Anyway, I need to work around this to be able to use Hibernate in a 3-tier
system. I can only have SQL created when an object is really dirty sinc
--- [EMAIL PROTECTED] wrote:
>
> You need to learn about the mysteries of the
> unsaved-value
> attribute :)
>
> Hibernate looks at the id value to determine if an
> object
> discovered by cascade is "new" or not. So, if you
> have an
> object with a Long identifier, set
> unsaved-value="null".
You need to learn about the mysteries of the unsaved-value
attribute :)
Hibernate looks at the id value to determine if an object
discovered by cascade is "new" or not. So, if you have an
object with a Long identifier, set unsaved-value="null".
Note that another approach is to save() the Item ex
