cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Gentry <mgen...@masslight.net>
Subject Re: Any way to check if object has really changed?
Date Tue, 24 Mar 2009 13:50:41 GMT
I totally misread that!  I guess I need more caffeine this morning.  A
long time ago I dug through the code that checked for changes, but I'd
have to go look at it again.  If you want to share the code, it might
help others in the future.

mrg


On Tue, Mar 24, 2009 at 9:46 AM, Andrey Razumovsky
<razumovsky.andrey@gmail.com> wrote:
> I have a reverse problem :) Artist is marked as change, and in fact it is
> not. I've wriiten an implementation of comparing to snapshot, can post if
> someone'll find it useful
>
> 2009/3/24 Michael Gentry <mgentry@masslight.net>
>
>> Well, the Artist object didn't really change.  Could you override
>> Artist's addToPaintings() (don't forget to call super) and record
>> somewhere that a change has been made?
>>
>> mrg
>>
>>
>> On Tue, Mar 24, 2009 at 6:16 AM, Andrey Razumovsky
>> <razumovsky.andrey@gmail.com> wrote:
>> > Imagine you have Artist and Painting entities. You create a new Paining
>> and
>> > attach it to existing Artist, then commit. The Artist object is marked as
>> > modified, so LifecycleListeners will fire for it, but in fact nothing
>> > changed in DB table (ARTIST). Is there any way to check if object has
>> really
>> > changed? I suppose I could iterate through all attrs and simple to-one
>> rels
>> > during lifecycle event, and compare values with cached snapshot of the
>> CDO,
>> > but this seems to be an ugly way..
>> >
>> > Thanks,
>> > Andrey
>> >
>>
>

Mime
View raw message