Hi Robin, Thanks for your comments. Yes, it's completely possible to have "with connection as transaction" to guarantee rollback if something goes wrong, or "with pool as connection" to make sure that connection is properly closed/returned back to tha pool, or even "with pool as transaction", etc. My farther suggestion is to keep a dedicated package, named, say, as "transitional", which will not be imported via the root __init__.py. If an SA user has the newest Python, (s)he would directly import that stuff. Such a package could become a permanent part of SA, even if sometimes it'd be empty.
Skip, yes, of course, "trigger" - thanks for correction. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
