Diez B. Roggisch wrote:
> > We went down the SO road because that's all that was available back
> > then.  The limitations of SO became apparent in the last few weeks, and
> > I am spending over 2 weeks getting our stuff converted over to SA.  SA
> > is TONS more versatile and does exactly what I want out of an
> > database-object mapper, so I recommend using that.  Activemapper or
> > TurboEntity will get you quickly up and running, and both should work
> > with brute-force SA tables/mappers.
>
> Out of curiosity: what are these limitations of SO? So far, it suited my
> (simple) needs, and no SA experience on this side of the monitor.
>
> Diez

Limitations include:

An *easy* way to build complex select queries

Multiple Inserts with one sql query.

Lack of future support by TG...

The list goes on....

I also find that sqlalchemy's documentation is considerably better than
that of SQLObject.  Do do some of the things I did with SO I had to dig
into the source code.  I've only looked at the source for ActiveMapper
since converting over.

-percious


--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to