that's definitely a bug and am looking into it. if you *dont* delete the object, then it shows up as "detached" and all that :)
On Feb 1, 2013, at 3:37 AM, Christian Theune wrote: > Hi, > > I'm trying to get my head around the attached scenario - unfortunately the > documentation and aunt Google weren't too helpful :/ > > My expectation (up until now) was that an object that I mark as deleted would > become useless for the application, similar to being detached after closing a > session. If you run the attached code with SQLAlchemy (0.7 or 0.8) then the > object stays alive, stays attached and the application can't see that it has > been deleted. > > Is this intentional? Am I holding it wrong? > > Thanks, > Christian > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > <sqlalchemy-issue.py> -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
