On Jun 20, 2007, at 6:12 PM, Mike Orr wrote:
Michael and I are still planning on a SAContext object which will make the model metadata-centric rather than sessioncontext-centric, while still dispensing sessions as needed. I guess this can go on top of your multi-engine config-parsing code. It will probably obviate the need to store engines under 'g' at all: engines will be in a SAContext object in the model. It's pretty straightforward, maybe I can get it done this week.
The 'g' thing is gone already in trunk. Having it fixed at the metadata also means you can use autoload=True I assume? Right now one needs to import create_engine and connect it before a table statement including autoload can even exist (which kind of sucks).
Is it OK to go to sqlalchemy.default.dburi for the main engine and sqlalchemy.other_db.dburi for additional engines? That would cut out a bunch of complexity parsing options both with and without a middle part.
I didn't see anything about who was working on a SAContext or its progress, which was the main motivation for me to start adding more methods into Pylons to handle loading configs well. Let me know the scope of what SAContext will cover so I can avoid any replication of work.
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature
