On Jun 29, 2006, at 2:55 PM, Kevin Dangoor wrote: > > Hi, > > I've just checked in my take on SQLAlchemy 0.2 support. My goals > were this: > > 1) Don't worry about backwards compatibility with previous SA support. > Instead, worry about doing it right > > 2) Make it easy to use both plain SA and ActiveMapper > > 3) Just having sqlalchemy installed does not mean that you want to use > SQLAlchemy all the time > > 4) SQLObject and SQLAlchemy in the same application is not a supported > configuration > > 5) Toss package-based dburis at this point. First Class will support > use of a different database for each application. If someone needs > multiple database engines and can help come up with a good config API > for that, I'm fine with that. > > The basic API is very simple. Set sqlalchemy.dburi in your config > file, then... > > from turbogears.database import metadata, session > > ...create your tables using that metadata... > > ...retrieve and update objects using that session... > > Still to do: > > * quickstart > * identity > * tg-admin sql > > > Thanks to everyone who has been forging ahead with SQLAlchemy support > and providing patches. That code and discussion has been very > informative. Let me know if there are holes or missing use cases in > what I've done.
Excellent! Thanks Kevin, going to try and break it see what happens... ;) Great job! Alberto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
