Persistant Objects


(David Corbin) #1

Is there library/framework for ruby that makes doing persistant objects
easy? At this point, I’m not in the least bit concerned about how the
back-end works (SQL, XML, proprietary). All I want is something where I
can store and reload a large conglomerate of interrelated objects with a
simple calls. I’d like to do this without an extensive learning curve,
or a lot of object customization. Support for migration between
different versions of the same classes is important.

I’ve looked through the RAA, but nothing jumped out at me. Google led
me to pstore (standard with ruby), but documentation seems to be
extremely scare on that.

Thanks for any pointers

David Corbin


(Joel VanderWerf) #2

David Corbin wrote:

I’ve looked through the RAA, but nothing jumped out at me. Google led
me to pstore (standard with ruby), but documentation seems to be
extremely scare on that.

PStore is fine for what it does, and it’s documented in the Pick Axe:

http://www.rubycentral.com/book/lib_standard.html

But it reads and writes the whole file for any transaction, which may
not be what you want…


(David Corbin) #3

Joel VanderWerf wrote:

David Corbin wrote:

I’ve looked through the RAA, but nothing jumped out at me. Google led
me to pstore (standard with ruby), but documentation seems to be
extremely scare on that.

PStore is fine for what it does, and it’s documented in the Pick Axe:

http://www.rubycentral.com/book/lib_standard.html

But it reads and writes the whole file for any transaction, which may
not be what you want…

You’re right, that’s not what I want. What I really want, now that I
thiink about it, is for objects to be loaded “on-demand”, and for dirty
objects to be periodically “flushed to disk”. I probably need to give
this some more thought, and I’ll probably end up simply doing a SQL
database, or XML.


(Torsten Rüger) #4

David Corbin wrote:

You’re right, that’s not what I want. What I really want, now that I
thiink about it, is for objects to be loaded “on-demand”, and for
dirty objects to be periodically “flushed to disk”.

That sounds to me like an OO database. Which does exactly that and it’s
really nice for the application programmer.
Unfortunately the only decent one I know is GOODS and that has no Ruby
interface yet. There is a perl interface for the bravehearted “porter”.
Goods does exactly this Schema evolution and copes with several clients
using different schemas. I’ve worked with only from java, and it’s
really nice, so just for information, here’s a URL
http://www.garret.ru/~knizhnik/goods.html.

Torsten


(Holden Glova) #5

Perhaps mneumonic fits your needs?
http://www.ruby-lang.org/en/raa-list.rhtml?name=Mnemonic


Signed,
Holden Glova

···

On Fri, 05 Jul 2002 03:10, David Corbin wrote:

Joel VanderWerf wrote:

David Corbin wrote:

I’ve looked through the RAA, but nothing jumped out at me. Google led
me to pstore (standard with ruby), but documentation seems to be
extremely scare on that.

PStore is fine for what it does, and it’s documented in the Pick Axe:

http://www.rubycentral.com/book/lib_standard.html

But it reads and writes the whole file for any transaction, which may
not be what you want…

You’re right, that’s not what I want. What I really want, now that I
thiink about it, is for objects to be loaded “on-demand”, and for dirty
objects to be periodically “flushed to disk”. I probably need to give
this some more thought, and I’ll probably end up simply doing a SQL
database, or XML.


(stefano) #6

Any volunteers for porting Enterprise Objects Framework to Ruby?

···

On Thu, 04 Jul 2002 17:14:12 +0200, David Corbin wrote:

You’re right, that’s not what I want. What I really want, now that I
thiink about it, is for objects to be loaded “on-demand”, and for dirty
objects to be periodically “flushed to disk”.


ste


(David Corbin) #7

Perhaps mneumonic fits your needs?
http://www.ruby-lang.org/en/raa-list.rhtml?name=Mnemonic

Mnemonic looks interesting. To clarify a few things, it looks like
whenever you construct an object you need to actually construct Mnemonic
wrapper around the object. Is that correct? Is there anyway to build
that into the business class, so that client’s don’t need to deal with
Mnemonic?

Thanks.

···

Signed,
Holden Glova
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9JU8b0X8w8X71zPcRAp9sAJ4gGuALMDzQnP5x4I7CpmfIH0YFewCfaMpO
euiIYWsobHJc5yhvLdPzzT8=
=mS4s
-----END PGP SIGNATURE-----