Re: [elephant-devel] 4th European Lisp Workshop

[Ian Eslick]

This sounds intriguing! I'm not sure what you mean by data model, however. Do you mean change the underlying backing store? It wouldn't be hard to add something like this into the MOP data access protocol. I think there are some interesting issues surrounding how to handle this in an online manner. I look forward to seeing what you come up with!

Ian


On Apr 11, 2007, at 1:25 PM, Pierre THIERRY wrote:

Scribit Robert L. Read dies 09/04/2007 hora 18:43:

However, if someone else can go, I am also happy to help or to
co-author a paper with them.

It occurred to me that the combination of persistence and the MOP goes

model.

That is, even a powerful macro system to build code that accesses a DB

based on the MOP can bring to stored data the dynamic nature of CLOS,
and you could completely change how data is organized, while the

process is automated (which is hard, I suppose), like cl-migrations.

Like Erlang, Common Lisp enables a system to remain live while being

almost for free.

I think this could easily make a short paper, maybe even a long one. I

point.

Quickly,
Pierre
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

far beyond anything else I know in terms of flexibility WRT to the data sets in stone the data model at compile-time. But a persistence library application runs, without having to build a migration tool, even if this updated at the code level. An Elephant-like persisence library enables a system to remain live while being updated at the data model level also, will try to write a first draft of it, and probably ask for help at some

PGP.sig
Description: This is a digitally signed message part

_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel