[elephant-devel] Design Suggestion Request

[Daniel Salama]

Granded. Now, your original suggestion addressed the issue of using  
collections in slots and instead of collections of objects, simply to  
use collections of references to objects, which make sense and in a  
way is somewhat along the lines of what indexes do (from a general PoV).

Not having looked at DCM yet, is it possible to just use the  
"persistence machinery" and DCM in a more seamless fashion? For  
example, if I declare a persistent CLOS class, can I hook that up to  
DCM and get the benefits of DCM and persistence at the same time?  
 From Ian's last statement, this doesn't seem possible yet, but I may  
be wrong.

Thanks,
Daniel

On Jul 27, 2006, at 2:07 PM, Robert L. Read wrote:

> A reasonable way to work is to use completely persistent objects  
> and see how the performance
> is for you --- LISP and elephant support this kind of rapid  
> prototyping extremely well.  I may be
> a bit old-fashioned---but I often find that I end up having to take  
> explicit control of the write-back
> policy in any case, and I personally never find having to remember  
> when to write things a burden,
> since they are almost always part of a "business rule", if your  
> using a 3-tiered application.
>
> On the other hand, you can follow your plan based on Ian's idea,  
> and similar layer on secondary
> indexes once prototyping shows that you need them.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20060727/48d86b40/attachment.html>