let me tell you about global_connect - as a feature, I dont think it really belongs in SA. It creates ambiguity about creating a Table object (metadata or no metadata ? isnt explicit better than implicit?) and also is a decidedly "frameworky" feature, in that its making a suggestion as to how to organize your application. its one of the leftovers from 0.1 that i couldnt manage to remove over the screams of those who wanted it to stay...but with two confused users just this week, its well on its way to the guillotine again....
to use it while also being able to disconnect, send it an engine: engine = create_engine(...) global_connect(engine) engine.dispose() but even better, is just use your own global DynamicMetaData object ! that way, no confusion. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
