For those who care, I have been helping a guy get TurboGears working with his ActiveMapper model, and I believe he has it working now. Here is his email from the sqlalchemy mailing list that describes how he sets up the connection. It appears that he creates his engine somewhere manually, and then sets it at the top of his model.py.
Begin forwarded message from [Charles Duffy] > Date: June 18, 2006 4:50:20 PM EDT To: > [email protected] Subject: Re: [Sqlalchemy-users] > ActiveMapper, DynamicMetaData, and TurboGears [SOLVED] > > I ended up doing this in my model.py: > > activemapper.metadata = BoundMetaData(engine) > > Since BoundMetaData, unlike the default DynamicMetaData, > doesn't try to make everything thread-local, I don't have other > TurboGears code (running in different threads) complaining > that it can't find an engine even though my model.py called > activemapper.metadata.connect(engine). -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
