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 behavi
the current implementation of unit of work has an identity map that is
weak referencing...as of the 0.3 series, the only time that the session
holds a strong reference is when an object is marked for deletion (and
its placed into a "deleted" list). this is different from the 0.2
series where item
