this is probably in a CHANGEs file somewhere but I forgot to add it to the migration notes. added as:
0.4 has an unfortunate default setting of "pool_threadlocal=True", leading to surprise behavior when, for example, using multiple Sessions within a single thread. This flag is now off in 0.5. To reenable 0.4's behavior, specify `pool_threadlocal=True` to `create_engine()`, or alternatively use the "threadlocal" strategy via `strategy="threadlocal"`. On Dec 10, 2008, at 6:41 PM, Robert Ian Smit wrote: > > Hi, > > I am porting our pylons app from 0.4.5 to 0.5. > > It appears that implicit queries are using a new connection instead of > re-using the existing one that is also used by the ORM Session. > > I have read the Migration Docs and looked at the changelog and didn't > find anything related to this matter. > > To avoid opening many connections or to re-use a transaction handle, I > had to rewrite code such as this > > from: > > s = select(....) > dbsession.query(Model).instances(s.execute()) > > > to: > > s = select(....) > list(dbsession.query(Model).instances(dbsession.execute(s))) > > Is this change expected or is it an indication of an error somewhere? > > Thanks, > > Bob > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
