On 3/16/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote:
ohhh then I'll have to learn tSQLAlchemy
ohhh i want to do that for some non-tg stuff, this is great news I may end up writing that in python
That seems really hard to accomplish, and i don't see it happening without another layer.
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.
ohhh then I'll have to learn tSQLAlchemy
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.
ohhh i want to do that for some non-tg stuff, this is great news I may end up writing that in python
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.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
