[Sqlalchemy-users] ProxyEngine refactored

[Jeff Watkins]

In order to support frameworks like TurboGears, I've refactored the ProxyEngine class into BaseProxyEngine and ProxyEngine. The BaseProxyEngine merely provides all the proxying logic, while ProxyEngine provides the thread-local storage aspect needed for WSGI. In addition, I added an AutoConnectEngine. You specify the normal create_engine parameters, however, the dburi parameter can be a callable. So you can define all your classes before you know what the dburi parameter should be. Finally, if Kevin "Dangerous" Dangoor permits, I'll commit basic support for SQLAlchemy to the TurboGears framework. This will allow you to declare a PackageEngine (think AutoConnectEngine that pulls it's dburi from a CherryPy config file) and be assured that your unit-of-work will be committed if the request is successful. I'm really excited about using SQLAlchemy with TurboGears -- especially combined with the ActiveMapper code. I've already made good progress putting together a sample application. -- Jeff Watkins http://newburyportion.com/ "Not everything that can be counted counts, and not everything that counts can be counted." -- Albert Einstein