From: Lyndon Samson <lyndon.samson@...>
Date: 2005-10-26T10:57:00+09:00
Subject: Re: The "perfect" ORM?

Ideally you'd be more generic than an ORM.

You'd start with objects.

1.Have some method of querying them ( and implicit in this is some
concept of unique ID/PK ).
2.Have some method of storing/retrieving them.
3.Have some form of collection which can contain the full object set
or a subset.

You could go overboard by being very abstract for 1&2 which would
allow you to utilise the storage engines query facility ( map to SQL
for example), or very low-level rubyesque ( blocks for filters on
properties etc ).

I don't think you should assume a RDBMS as the persistence mechanism.

Also, db4o is worth looking at, it uses QBE.

cheers
lyndon