Something I've realized is that all objects are cascading from a large
one. There's a large "staff" object, which then has a collection of
"people" objects which then have a collection of "people statistics"
objects. This might well be the problem. If so, how can I tell SQLA to
commit to the database and wipe clean it's memory? Is Session.remove()
supposed to do this?

Chris
--~--~---------~--~----~------------~-------~--~----~
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 
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to