this has to do with the structure of your objects prior to the flush.   
the answer lies in the objects being constructed and added, as well as any
connections created or broken between objects loaded into the current
session.


Gloria W wrote:
>
> Just a quick update: A forced flush between queries does no good.
> Creating a new instance for each query seems to be the only immediate
> cure.
> >
>


--~--~---------~--~----~------------~-------~--~----~
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