Database to objects mapping library

Hello

I am looking for a database to objects mapping library (smth like EOF,
Hibernate or Cayenne for Java). Is there anything I should be interested
in?

···


Marek Janukowicz

Here is a persistence library I threw together in a hurry, which so far
doesn’t work too badly. Instead of using a hash to define the persistence
mappings, perhaps a YAML configuration file could be consulted.

I haven’t put it up on RAA because I haven’t written decent tests or docs
for it.

The link:
http://www.io.com/~egabriel/spl.rb

–gabriel

···

On Tue, 07 Jan 2003 14:31:49 +0000, Child wrote:

Hello

I am looking for a database to objects mapping library (smth like EOF,
Hibernate or Cayenne for Java). Is there anything I should be interested
in?

i also have one you may be interested in. it is a part of Jigsaw which is a
development oo-db/web framework i’ve created for creating my professiojnal
accounting application. its not quite done but has come along nicely and
should be ready fort a first realease in a few weeks.

db / object mapping is done simply be using the same attribute names as the
field names in you database table. if that is a problem all you require is to
create a go between object that maps the two together.

sure has made my life easier. let you know when i let it loose to the wild.

-transami

···

On Tuesday 07 January 2003 01:12 pm, Gabriel Emerson wrote:

Here is a persistence library I threw together in a hurry, which so far
doesn’t work too badly. Instead of using a hash to define the persistence
mappings, perhaps a YAML configuration file could be consulted.

I haven’t put it up on RAA because I haven’t written decent tests or docs
for it.

The link:
http://www.io.com/~egabriel/spl.rb

–gabriel

On Tue, 07 Jan 2003 14:31:49 +0000, Child wrote:

Hello

I am looking for a database to objects mapping library (smth like EOF,
Hibernate or Cayenne for Java). Is there anything I should be interested
in?


tom sawyer, aka transami
transami@transami.net

                               .''.
   .''.      .        *''*    :_\/_:     .
  :_\/_:   _\(/_  .:.*_\/_*   : /\ :  .'.:.'.

.‘’.: /\ : ./)\ ‘:’* /\ * : ‘…’. -=:o:=-
:/:‘.:::. | ’ ‘’ * ‘.'/.’ (/’.‘:’.’
: /\ : ::::: = / -= o =- /)\ ’ *
‘…’ ‘:::’ === * /\ * .‘/.'. ‘._____
* | : |. |’ .—"|
* | _ .–’| || | _| |
* | .-‘| __ | | | || |
.-----. | |’ | || | | | | | || |
__’ ’ /“\ | '-.”". ‘-’ ‘-.’ '` |.

also i should note that it is essentially a one-to-one coorespondence, i.e.
class<->table (object<->record), but it does handle subrecords (one-to-many)
relationships between tables quite seemlessly. also, you can also alias your
attributes to map them to the database fields if they differ in name.

···

On Tuesday 07 January 2003 04:43 pm, Tom Sawyer wrote:

db / object mapping is done simply be using the same attribute names as the
field names in you database table. if that is a problem all you require is
to create a go between object that maps the two together.


tom sawyer, aka transami
transami@transami.net

                               .''.
   .''.      .        *''*    :_\/_:     .
  :_\/_:   _\(/_  .:.*_\/_*   : /\ :  .'.:.'.

.‘’.: /\ : ./)\ ‘:’* /\ * : ‘…’. -=:o:=-
:/:‘.:::. | ’ ‘’ * ‘.'/.’ (/’.‘:’.’
: /\ : ::::: = / -= o =- /)\ ’ *
‘…’ ‘:::’ === * /\ * .‘/.'. ‘._____
* | : |. |’ .—"|
* | _ .–’| || | _| |
* | .-‘| __ | | | || |
.-----. | |’ | || | | | | | || |
__’ ’ /“\ | '-.”". ‘-’ ‘-.’ '` |.