thanks, this is a simple issue that appears to be throughout the 0.6 series
only, resolved in r26f423a667ca which you can get at
http://hg.sqlalchemy.org/sqlalchemy/archive/26f423a667ca.tar.gz .
On Oct 26, 2010, at 2:41 PM, Lenza McElrath wrote:
> Thanks for the quick response Michael.
>
> I
Thanks for the quick response Michael.
I do not know why all references to the object are lost. Adding the asserts
you suggested shows that the object is in the session and in the dirty list
as expected.
I have been able to reproduce the issue with a simple test case. I have
untangled it from m
On Oct 25, 2010, at 1:07 PM, Lenza McElrath wrote:
> I am running into a issue where it looks like SQLAlchemy is not performing
> the proper DB update when committing a session after modifying an object.
> This happens only when all references to the updated object are lost, and I
> update a
I am running into a issue where it looks like SQLAlchemy is not performing
the proper DB update when committing a session after modifying an object.
This happens only when all references to the updated object are lost, and I
update a mutable attribute BEFORE updating another attribute. It seems as
