SQLObject or SQLAlchemy?

[Bruno Desthuilliers]

Re: SQLObject or SQLAlchemy?

lazaridis_com wrote:

Ο/Η Bruno Desthuilliers Îγραψε:

>lazaridis_co m 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 "persistenc y 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').

good night.
--
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in 'onurb@xiludom. gro'.split('@')])"

[lazaridis_com]

Re: SQLObject or SQLAlchemy?

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 "persistenc y 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)."

http://case.lazaridis.com/wiki/Persist

..

[alex23]

Re: SQLObject or SQLAlchemy?

lazaridis_com wrote:

The "persist case" evaluates python persistency systems (or
mechanisms), and will show my personal preference:

Do you feel that evaluating-for-evaluation's-sake produces a more
measured understanding of the value of a product than that taken from
its use in, say, actual development?

-alex23

[Bruno Desthuilliers]

Re: SQLObject or SQLAlchemy?

lazaridis_com wrote:

Bruno Desthuilliers wrote:

>lazaridis_co m wrote:

>>Ο/Η Bruno Desthuilliers Îγραψε:
>>>lazaridis_co m 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
>>>>>wonderin g 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 "persistenc y 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.

Of course not.

"I'm just wondering what everyone's preference is, and why, and if
there are even more choices for ORM."

You may not know it but the R in ORM stands for Relational, which
actually implies a RDBMS.

The "persist case" evaluates python persistency

Once again, it has nothing to do with persistency. I can use an ORM
connected to an in-memory SQLite db.

systems (or
mechanisms), and will show my personal preference:

I don't give a damn about your "personal preferences".

--
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in 'onurb@xiludom. gro'.split('@')])"

[lazaridis_com]

Re: SQLObject or SQLAlchemy?

alex23 wrote:

lazaridis_com wrote:

The "persist case" evaluates python persistency systems (or
mechanisms), and will show my personal preference:

>
Do you feel that evaluating-for-evaluation's-sake produces a more
measured understanding of the value of a product than that taken from
its use in, say, actual development?

I don't evaluate for "evaluating-for-evaluation's-sake", see the home
page of the project:

"The project selects Open Source Subsystems for integration into a
Coherent Software Production System. "

http://case.lazaridis.com/wiki

..

[lazaridis_com]

Re: SQLObject or SQLAlchemy?


Bruno Desthuilliers wrote:

lazaridis_com wrote:

Bruno Desthuilliers wrote:

lazaridis_com wrote:
>Ο/Η Bruno Desthuilliers Îγραψε:
>>lazaridis_c om 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 areeven
>>>>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 "persistenc y 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.

>
Of course not.

You are right.

It's not relevant for _you_.

"I'm just wondering what everyone's preference is, and why, and if
there are even more choices for ORM."

>
You may not know it but the R in ORM stands for Relational, which
actually implies a RDBMS.

....which is completely irrelevant to _me_.

Thus I'm looking for an ORM which decouples the "R" part nicely.

The "persist case" evaluates python persistency

>
Once again, it has nothing to do with persistency. I can use an ORM
connected to an in-memory SQLite db.

What _you_ do is not _my_ use case.

systems (or mechanisms), and will show my personal preference:

>
I don't give a damn about your "personal preferences".

_You_ are not the central part of this topic.

_I_ am not the central part of this topic.

The OP asked for "personal preferences":

"I'm just wondering what everyone's preference is, and why, and if
there are even more choices for ORM."

I present my personal preferences here:

http://case.lazaridis.com/wiki/Persist

nothing special.
..