At 01:30 PM 6/28/01 -0400, Jeff Kowalczyk wrote:
> > I was thinking there would be a default table where everything gets
> > stored by default.  A programmer then tells the ORMapping about
> > specific classes and how to store them.
>I wouldn't think it would be practical to use unless the ORMapping
>managed the tables by examining the class signature as metadata. ADO.NET
>has this in reverse, the tools can define classes that mirror a SQL
>recordset. Similarly, references to other objects would need to be
>supported with joins.
>BTW, I was going to mention this article
>As a 'rah-rah zope' example of RDBMS complexity Zope/ZODB spares us, but
>now it brings up something the ORMapping layer would have to do (perhaps
>with more savvy) to support mixed folder hierarchy among class

You might want to look at the DBObjects/SmartObjects development. DBObjects 
already allows direct ORMapping, including more restrictive QueryFolders, a 
History with Undo functionality (in CVS), Volatile/Persistent Mode, XML-RPC 
Support and much more.
DBObjects Home Page:
(Note: The DBObjects Demo is using the older versions.)
DBObjects CVS:

Accessing the CVS via SSH:
cvs -d ":pserver:[EMAIL PROTECTED]:/cvs" login
password anonymous
cvs -d ":pserver:[EMAIL PROTECTED]:/cvs" checkout DBObjects

I am not the CVS expert, so let me know if it does not work.


Stephan Richter
CBU - Physics and Chemistry Student
Web2k - Web Design/Development & Technical Project Management

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to