SQLObject or SQLAlchemy?
ilias at lazaridis.com
Tue Sep 5 15:32:23 CEST 2006
Bruno Desthuilliers wrote:
> lazaridis_com wrote:
> > Ο/Η Bruno Desthuilliers έγραψε:
> >> lazaridis_com wrote:
> >>> John Salerno wrote:
> >>>> Are there any major differences between these two? It seems they can
> >>>> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> >>>> wondering what everyone's preference is, and why, and if there are even
> >>>> more choices for ORM.
> >>>> Thanks.
> >>> You can review the Persit Case, which will shortly evaluate the stated
> >>> ORM's:
> >>> http://case.lazaridis.com/wiki/Persist
> >>> It is possibly of importance to remember some requirements which should
> >>> be relevant for an persistency mechanism targetting an OO language:
> >> RDBMS are not "persistency mechanism", they are data management tools.
> > possibly.
> > but this is not relevant, as the "Persist" case does not deal with
> > RDBMS.
> Then your post is irrelevant since there's a clear indication that the
> OP question was about RDBMS integration in Python (hint: SQLObject and
> SQLAlchemy both start with 'SQL').
Of course it's relevant.
"I'm just wondering what everyone's preference is, and why, and if
there are even more choices for ORM."
The "persist case" evaluates python persistency systems (or
mechanisms), and will show my personal preference:
"Object Oriented Persistency Systems (this includes OODBMS,
Object-Relational-Mappers, and others)."
More information about the Python-list