Re: CLOS persistence

On jan. 2, 18:22, vtail <victor.kryu...@xxxxxxxxx> wrote:
Thank you for your answers, Levy.

Congratulations on winning the contract - it is impressive what you
have done under such time constraints!

If it's appropriate to ask - what was the reason for writing cl-perec
in the first place (versus using elephant)? I understand that your
time constraints were pretty tight so you most likely have studied all
the available options before rolling your own thing...

Best Regards,
Victor.

Obviously we have not written cl-perec in that three months but in the
past two years (with many other things in parallel). At that time
elephant was in a very early stage and it's RDBMS mapping was well at
least hard to explain to people. I don't know if that changed by now
but I don't think so. The BDB backend was not an option due to its
licensing and the fact that most people here are happy when they see
their data stored in RDBMS rather than in X.

There was clsql and allegrocache too and I evaluated both.
Allegrocache was 1.0 at that time and had some very nice features but
we decided not to use it due to its price and not being RDBMS based.
Using lisp in itself is enough to explain and we didn't want to go
into this other issue. As for clsql we had quite a few problems with
it (and it's not really a CLOS persistence layer), enough to roll our
own RDBMS layer called cl-rdbms.

levy
.