Hi Michael,
Thanks for the answers.
> also, when you say you "triggered" the problem, can you do that
> predictably ? can you send a small test program that does it every
> time ? otherwise it sounds like a threading thing (if thats at all
> possible).
>
Very much so. Everytime I run my budding application I trigger the problem.
>is there any chance the Connection youre using is being shared
>between threads ? thats also not supported.
Hmm Interresting question.... As you can see from the code snippet I sent
previously, I am using PyQt. Hence that is multithreaded. I hadn't thought
about it, but since the data processing is being run by some dynamically
created widget, it is essentially run in a different thread.
I moved the "connect" to the method handling the data and the problem
disappeared.
It would be easy enough to make sure all the "flushes" are done in a single
thread of execution, but can you share a session across multiple thread if
you ensure that anything dealing with connection (most methods of the session
save maybe for "save") are executed by a single thread? IOW if you modify an
object belonging to a session in a different thread, will the session notice?
Regards,
François
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sqlalchemy
-~----------~----~----~----~------~----~------~--~---
