[EMAIL PROTECTED] wrote:
Yes, I'm glad you raised this Ara, there are a couple of different
things I've been speculating about here:
(1) An isDirty() interceptor callback, to allow an application to
implement its own dirty checking algorithm
(2) A new property attribute; update=never|auto, to
What about a isModified()? For tracking modification. Is it possible to
add a modification-tracking=true to a class/ and let Hibernate
decide whether an object is modified (a setter method actually changed a
property, etc) and then only update that modified object and that
specific field only?
:
23/01/03 07:43 Subject: Re: [Hibernate] saveOrUpdate()
PM
] To: [EMAIL
PROTECTED]
Sent by:cc:
[EMAIL PROTECTED] Subject: RE: [Hibernate]
saveOrUpdate
Ummm theres a bunch of things to get right and since I can't see your
mappings, I'm not sure which. However, you should check out the
functionality of:
* unsaved-value attribute of id
* cascade attribute of associations
* lazy attribute of collections
* proxy attribute of class, subclass,
