[sqlalchemy] Re: Object is already attached to session

I am running into similar problems, adding to the complexity the threadpool module. Here's a post that might help: http://blog.uxpython.com/blog/web/view/116 I am still running into problems, however, based on parent/child relationships... i think the answer lies in the sqlalchemy `cascade` prop

[sqlalchemy] sqlalchemy sessions, Queue

I've got a thread that creates a new instances (connected to a realtime interface), a main thread, and a pool of threads that *does stuff* to my instances. After *the stuff* is done, they usually get written to the database by the main thread. What's the right way to remove these things from what