Kevin Dangoor wrote: > Hi Michele, > > Thanks for forwarding that. I hadn't seen that particular posting, but > I did read about SQL Soup on the sqlalchemy list. Nice stuff (though I > still with an ORM myself :) >
Yep, me too, but it's really nice (as Ian said on his post) to take any existing db and be able to use it with SQLAlchemy in such a straightforward way. :-) > By the way, I exchanged a couple messages with Mike Bayer a couple > weeks ago about SQLAlchemy's status. It sounds like SQLAlchemy is > actually pretty well baked at this point. To make an "official" switch > requires > > 1) a migration path for current users > 2) New versions of CatWalk/Model Designer/tg-admin sql > > Since TurboGears already features some support for SQLAlchemy, these > things can be tackled any time. (Of course, potentially destabilizing > changes don't belong on the trunk... I guess the more times I say > that, the more that means I should really just do the branch thing.) > Yep, probably food for FirstClass (am I right?), I was wondering today (also inspired by Mark [1]) how much difficult could it be to write a SQLObject wrapper that maps things to a SQLAlchemy database for backward compatibility, the most difficult thing is probably the query mechanism and SQLBuilder, but I've not used SQLObject or SQLAlchemy that much so I'm probably plain wrong. Ciao Michele [1] http://compoundthinking.com/blog/index.php/2006/04/10/python-database-projects-arise/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
