From: Anders Borch <spam@...>
Date: 2003-04-27T22:13:23+09:00
Subject: serializing objects to sql

Last night I was wondering why I had to write sql code to store all my 
ruby classes in my database. It seemed to me that all the nifty features 
that let us inspect objects could be used to serialize objects in a 
transparent manner...

I wrote a short "proof of concept" like piece of code and put it here:
http://darkside.deck.dk/sql-serialize.rb

The general idea is that by mixing in my module and calling 
insert/update/delete on the object you will get an array of sql 
statements which you then could pass to a DBI instance for persistance.

This is nowhere near finished, but I would LOVE to get some feedback, on 
this code. Is the idea usable at all? I read some of the posts here on 
persistent objects, and some of them seem to be a lot more elegant than 
my code, but none of them let me easily use a database.

once again: lots of feedback please. is the world interested in stuff 
like this? are there some fatal flaws I have overlooked which will doom 
this project? is there any reason why I haven't put this on sourceforge yet?

/Anders