Re: CLOS persistence
- From: Ken <kennynospamtilton@xxxxxxxxxxxxx>
- Date: Thu, 15 Nov 2007 00:17:36 -0500
Slobodan Blazeski wrote:
On Nov 13, 3:07 pm, Ken <kennynospamtil...@xxxxxxxxxxxxx> wrote:Joost Diepenmaat wrote:On Tue, 13 Nov 2007 08:15:42 -0800, Javier wrote:Is Rucksack dead? ktI've got some classes, with millions of instances. So much that it isI've been looking around for a persistence library lately, and as far as
easy to get running out of memory.
My simple question is:
Is there any way to manage all of this clases through a database? I'm
not saying just persist them, but also getting them out of memory so I
can work from the database when needed? I don't want to reimplement all
of the program, I'm looking for a solution like MOP or something like
that.
Any help?
I can tell, clsql is /probably/ good enough to do this. It has a fairly
basic (but apparently sane and straight-forward) OO-relational mapping
and the documentation seems to be quite good.
Seehttp://clsql.b9.com/
I've also had a look at cl-perec, and it looks a lot fancier, but the
documentation is pretty much non-existent (or it may be just hard to find)
Anyway, I can't tell you anything about the memory efficiency of either -
maybe someone else can tell you more, or just try it out yourself.
Joost.
Author doesn't have time to develop it, though concept is very
interesthing.
uh-oh. Has Lisp open software proven that Franz is worth the <gasp> price? [Cue the bolsheviks]
Me, I'm hot for Allegrograph. Anyone know of an open source RDF implementation with a C API?
kzo
.
- Follow-Ups:
- Re: CLOS persistence
- From: Slobodan Blazeski
- Re: CLOS persistence
- From: D Herring
- Re: CLOS persistence
- From: Ken
- Re: CLOS persistence
- References:
- CLOS persistence
- From: Javier
- Re: CLOS persistence
- From: Joost Diepenmaat
- Re: CLOS persistence
- From: Ken
- Re: CLOS persistence
- From: Slobodan Blazeski
- CLOS persistence
- Prev by Date: Re: quote semantics
- Next by Date: Re: Cluster-by challenge
- Previous by thread: Re: CLOS persistence
- Next by thread: Re: CLOS persistence
- Index(es):
Relevant Pages
|