i will grant that this behavior is sub-optimal, and also that its in conflict with the docs - I have just updated the docs on the site to represent this current behavior:
http://www.sqlalchemy.org/docs/unitofwork.myt#unitofwork_changed im not exactly sure of a clean way to restore the 0.2 behavior, the only option seems to be a "__del__" handler on the identity map weakvaluedictionary that scans garbage-collecting objects for changes and adds them to a persistent collection...but in my experience anytime you start working with __del__ the stability of the application plummets (due to its asynchronous nature...) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
