Michael Bayer wrote: > the most likely cause is the "threadlocal" mod is being imported > somewhere in the production application. this creates a > SessionContext that is globally associated with all mappers, and is > used when new object instances are created. > > try to see if "sqlalchemy.mods.threadlocal" is imported anywhere and > remove it. > > another cause is if youre using a SessionContext yourself, either > with assign_mapper or as an extension to mappers, but that would be > pretty obvious. >
Is there a way to verify through introspection that threadlocal is in use? Randall ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
