<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
On Thu, 2006-07-27 at 14:23 -0400, Daniel Salama wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">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.</FONT><BR>
<BR>
</BLOCKQUOTE>
<BR>
No, that isn't possible.<BR>
<BR>
It is possible to design a CLOS structure first (without the concern of persistence), and then with a very <BR>
small amount of work, use direct persistence and slot-based indexing and functional indexes if necessary <BR>
to make everything persistent. It would then be reasonable to "switch-over" to a DCM based system<BR>
by making those classes inherit from "managed-object" instead. It would not take too much work...<BR>
maybe a few hours...to move back and forth between the two ideas. But they cannot be simultaneously<BR>
employed in any useful way.<BR>
<BR>
Actually one of the great things about Elephant is that it allows you to change, or delay, these kind<BR>
of implementation decisions as much as possible---for example, which technology you use as the <BR>
back-end database.<BR>
<BR>
<BR>
<BR>
</BODY>
</HTML>