Michael Bayer wrote:
On Sep 20, 2007, at 12:55 PM, Alexandre Conrad wrote:
It turns out that even if the values were kept unchanged, the slot
get's
ditry. Of course, I'd understand that as soon as the setattr() is
called
against the slot, it automaticly gets dirty regardless of the
replaced data.
it shouldnt. "dirty" changes are based on a comparison of the new
value being different from the old value. send me a short test
script (since im catching up on 500 emails...also what SA version ?)
Test case attached. I'm using SQLAlchemy-0.4.0beta6dev_r3502.
Regards,
4 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: session.dirty, not b...
.py