yeah OK, update to r3514 and call Session.is_modified(instance). check the docstrings on the "Session" class for options. you're right, the dirty list is only going on a flag thats set for every setattr operation. it would be too expensive to do the comparison on every setattr so the docstring there is updated.
On Sep 24, 2007, at 10:08 AM, Alexandre Conrad wrote: > 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, > -- > Alexandre CONRAD > > > > <test.py> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
