[sqlalchemy] expunge cascade behavior change

Somewhere between 0.6.4 and 0.7.5, the expunge cascade behavior changed. Can you help me understand what changed/point me to the ticket? The attached script assertions succeed in 0.6.4 but the last one fails in 0.7.5. It doesn't seem wrong, but I'm wondering what the behavior was defined as

[sqlalchemy] Expunge

If I retrieve data strictly for reporting or other read-only use, e.g. the session will not be used to update data, should I expunge the objects returned by the query from the session? If I just let the session object go out of scope is that sufficient? Thanks, Mark -- You received this

Re: [sqlalchemy] Expunge

On 2010-09-25 2:29 PM, Mark Erbaugh wrote: If I retrieve data strictly for reporting or other read-only use, e.g. the session will not be used to update data, should I expunge the objects returned by the query from the session? If I just let the session object go out of scope is that

[sqlalchemy] expunge vs clear

I'm using an orm configuration with a sessionmaker().mapper doing the mapping between my classes and my metadata. The documentation says that doing a Session.clear() should do the equivalent of a Session.expunge(inst) for all instances attached to the session. I have one instance attached to