[Zope] Nested hashes, ZopeDB bloat, and URL

[Dieter Maurer]

chrisf writes:
 > ...
 > Since we are talking about a couple thousand proteins and a over a
 > million atoms, I don't want to make anything under Family a proper zope
 > object.
 > I have seen ZopeDB bloat and its is not pretty.
 > 
 > Yet because they are not proper objects, they can not be refered to on
 > the URL or otherwise.
 > ie  http://whatever:8080/Family/Subfamily/Protein/Amino/Atom
 > everything bounces back to the one true product Family
When a relational database it adequate to store your data
(i.e. it is highly structures, essentially a collection of attribute
values of simple type), then you can put them in
a relational database and access them with ZSQL Methods.

  The direct traversal facility of ZSQL Methods (see "Advanced" tab;
  maybe the Zope Book) can make database records URL accessible.

  The "Brain Class" facility (or acquisition) can may ZSQL wrapped
  database records have interesting behaviour.

 > Session variables ?
No.

 > Operator overloading __call__, __getattr__?
Maybe.
 > Aquistion ?
Not bad.


Dieter