Hi Shane,

--On Donnerstag, 10. Mai 2001 11:32 -0400 Shane Hathaway 

> But storage of binary pickles was never the intention anyway.  I created
> a little interface that would allow you to store different classes in
> different PostgreSQL tables.  Before I got to implementing anything,

Is this much like the ZPatterns approach?
Or do we want to make some automatism to get tables created and destroyed
according to ZClasses needs?

> though, I had to move to another project.  But the file "sketch" shows
> (I hope) what I had in mind for making this work: programmers would call
> a bunch of functions that would put together a relational mapping tree.
> Now, in our discussion yesterday we decided ORStorage wasn't the right
> way to achieve relational mapping because there is no way for the
> database storage layer to have any context just given an OID.  If we
> instead consider writing a replacement for the stuff that's mainly in
> Connection.py, life gets a lot simpler.  At this level it *is* possible
> to know the parent OID of an object, though the current codebase does
> not use this opportunity.  Also, we wouldn't have to pickle and unpickle
> unnecessarily.
> So, if we have context, the relational mapping tree can work.  It would
> turn Zope into a purely relational application server, which a lot of
> folks apparently want.  ;-)

Oh, do they? ;)
Me dont :-)


Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to