A way to approach how this would be useful would be to contrast different use
environments for ZODB code.
The same code could be used for:
- Unit testing, prototyping, and general exploration could use ZODB with
DemoStorage and the default Connection objects.
- Production use could make use of ZODB and custom Connection objects that
map to/from relational tables.
On Monday 14 May 2001 09:51, Chris Withers wrote:
> Shane Hathaway wrote:
> > I'm telling you there's a lot more you can do with the code that makes
> > The next thing to do is to write a fishbowl proposal.
> This sounds cool but made my head hurt :-S
> Can you try and bring this back down to the level of us mere mortals by
> explaining how your OR stuff would let me take a table of data in an RDBMS
> table and have it appear as objects in the Management Inteferace?
> I know that's horribly oversimplified, but some of us only have small
> brains ;-)
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope )
. . . . . . . . . . . . . . . . . . . . . . . .
John D. Heintz | Senior Engineer
1016 La Posada Dr. | Suite 240 | Austin TX 78752
T 512.633.1198 | [EMAIL PROTECTED]
w w w . d a t a c h a n n e l . c o m
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -