openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evan Ireland" <eirel...@sybase.com>
Subject RE: Forced getter/setter access
Date Wed, 04 Apr 2007 19:48:55 GMT
Ok, this sounds good. 

> -----Original Message-----
> From: Abe White [mailto:awhite@bea.com] 
> Sent: Thursday, 5 April 2007 2:29 a.m.
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Forced getter/setter access
> 
> 
> > I meant "tuned" as in not including columns in the SQL update "set"
> > clause if they weren't really changed by the app (even if a 
> setter was 
> > called, the old and new values may be the same).
> 
> We detect when you're setting a field/property to the same 
> value it already has.  That doesn't require a state snapshot 
> or comparisons at flush time.  It just requires passing the 
> current value along with the new value to the internal method 
> that is responsible for "dirtying" the object.
> 
> Notice:  This email message, together with any attachments, 
> may contain information  of  BEA Systems,  Inc.,  its 
> subsidiaries  and  affiliated entities,  that may be 
> confidential,  proprietary,  copyrighted  and/or legally 
> privileged, and is intended solely for the use of the 
> individual or entity named in this message. If you are not 
> the intended recipient, and have received this message in 
> error, please immediately return this by email and then delete it.
> 


Mime
View raw message