Hi Ken, We never performed such check, and 4.0 is no exception. The reason is performance. We defer it until commit, hoping it will be fewer checks to do if say the same object is modified multiple times.
It is easy to redefine this behavior by overriding "DataObject.writeProperty(..)" and friends in your own superclass. Andrus > On Apr 27, 2018, at 6:31 PM, Ken Anderson <[email protected]> wrote: > > It *seems* like Cayenne (4.0) doesn’t check to see if a property being set is > different from the prior value before making the object dirty. Is that a > correct observation? If so, is there a reason it doesn’t? > > Thanks, > Ken > Confidentiality Notice: This e-mail and accompanying documents contain > confidential information intended for a specific individual and purpose. This > e-mailed information is private and protected by law. If you are not the > intended recipient, you are hereby notified that any disclosure, copying, or > distribution, or the taking of any action based on the contents of this > information, is strictly prohibited.
