On 3/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > just me. I can't label SQLAlchemy *the* ORM for TurboGears until it > > handles the easy cases easily, has backwards compatibility for people > > who started with SQLObject and want to move up, and has support of the > > Toolbox and tg-admin. > > Won't hold my breath for that. :-)
It's too long for a breath-holding, but I suspect it will be within 2006. > > Does that seem reasonable? > > Yes, all makes sense. I suppose as an end user/app writer I'd have been > happier if SQLObject was having it's warts treated on an incremental release > basis. I don't know if it was so broken that it needed a complete rewrite > rather than staged refactoring. That means SQLObject2 is going to need a > good deal of testing and running-in before it's ready for use in production > systems. Quite a way of I think. There's a couple things at work here. Certainly *some* of SQLObject's warts could be fixed incrementally. (And I'm sure patches would be accepted!) But, I think Ian's choice of starting from scratch and his approach of breaking out SQL generation from the OR layer are probably the right way to correct some deeply ingrained aspects of SQLObject. SQLObject has a large suite of tests which makes the move a bit more practical as well. That said, SQLAlchemy has a significant head start on SQLObject2. Additionally, it uses the "Data Mapper" pattern rather than the "Active Record" pattern (which is what SQLObject uses). This means that SQLAlchemy can handle a wider variety of scenarios and do interesting things like map a couple of fields from a SELECT to some object. My point for end users is this: you can start with SQLObject, which has API stability and broader support from TurboGears tools. Later on, your code should continue to run with only minor changes under SQLAlchemy. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
