> It's clear that the tg team can not make the transition from sqlobject > to sqlalchemy any easier, so I'm definitely not arguing for that. What > I'm saying is that if many users are in the same boat (transition to > 2.x from 1.x would be easy from a framework point of view, but hard > from an ORM point of view because of the sqlobject - sqlalchemy > transition) then perhaps not so much emphasis needs to go into > creating stepping stones such as 1.1 and 1.5. But maybe many other > users are not ORM limited, they perhaps really need stepping stones > for the framework itself.
One thing which I have been relying on a motivated user to do is to provide an SQLObject based TG2 example. I mean there's no reason at all why we can't support SQLObject in tg2, all that would be needed on the framework side is to provide a transaction interface for SO for repoze.tm, and that's not rocket science. Heck, it may even be done: http://codespeak.net/z3/sqlos/ We might also want to provide a sample template for an SQLObject project, and possibly an AppConfig subclass, but I don't think any of those things are that difficult, it's just that I switched all my projects over to SA a long time ago. --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 -~----------~----~----~----~------~----~------~--~---
