Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-Id: <C9CE2E23-18EC-4317-90DD-A58595DA5354@objectstyle.org>
From: Andrus Adamchik <andrus@objectstyle.org>
To: user@cayenne.apache.org
In-Reply-To: <5adb61290903240636y50314e89u537573e44132eeb9@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Any way to check if object has really changed?
Date: Tue, 24 Mar 2009 15:47:32 +0200
References: <3219fff70903240316o4644e474ia669ea819510ef9f@mail.gmail.com>
 <5adb61290903240636y50314e89u537573e44132eeb9@mail.gmail.com>

I think Andrey wants to do the opposite (??) - detect "phantom"  
changes that transfer an object to the MODIFIED state, but do not  
result in a DB record update.

Andrus

On Mar 24, 2009, at 3:36 PM, Michael Gentry wrote:

> 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
>>
>