I'm using ActiveMapper for my TurboGears model. All appears well (pretty much), but I have issues with the engine (set with activemapper.metadata.connect() in the model.py) being unavailable when other threads interact with the model (either during startup -- when the identity code is trying to generate tables -- or during actual web requests). This seems very much in line with what the DynamicMetaData class (which activemapper.metadata is an instance of) is designed and expected to do (maintain thread-local engine/metadata mappings), so I'm unclear on what the most appropriate way to specify the engine to use for other threads is. (I'm also trying to use metadata other than activemapper.metadata, such as to have a metadata object which doesn't do the thread-local engine thing; however, I'm having some trouble with that which I'll be describing in a second post momentarily).
Any hints? (If this belongs on the TurboGears list rather than the SQLAlchemy one, btw, do let me know). _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
