> Thanks Florent and Christopher for stepping in. At least now people can > discuss the merit of their favorite ORMs without wondering what the TG > team will do. Thanks for clarifying things, I appreciate.
I'll just put my 2 cents in as well. I have yet to see any compelling reasons to use Storm over SQLAlchemy, particularly if you already know SQLAlchemy. There may be reasons, having to do with multi-database support, but they aren't enumerated in the tutorial, and aren't explained clearly anywhere on the net. And I have every confidence that these features (whatever they are) will eventually be integrated into SQLAlchemy if they really are valuable. As for non-default turbogears integration options, I don't see anybody (other than canonical) with lots of legacy Storm models, so I'm not worried about making sure that Storm users have an easy route into TurboGears/pylons. So, at this point I'd vote for doing nothing. If they turn out to be a big hit, I can see supporting them as a non-default-option and an quickstart option like SQLObject in tg2. Anything beyond that world require that the Storm people provide some compelling technical advantages that can't/won't be added to SQLAlchemy, and an easy upgrade path for SQLAlchemy users, and I don't see that happening any time soon. --Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
