[ZODB-Dev] reasons to use ZODB

[Kapil Thangavelu]

there seems to be emphasis of audience on those familiar with relational
databases. relational programmers are used to thinking of tables as
containers, in the examples the table class, is what a relational
programmer would call a row. perhaps reworking the examples to have a
separate Table container class, and separate Row class would be more
appropriate.

cheers,

-kapil

On Mon, 2004-03-01 at 22:57, Duncan McGreggor wrote:
> On Mar 1, 2004, at 6:07 PM, Christian Robottom Reis wrote:
> 
> > On Mon, Mar 01, 2004 at 05:36:18PM -0500, Duncan McGreggor wrote:
> >> If you'd like to take a look at it, it's about half-way done (still
> >> have to do the 'tools' section, backups, and ZEO):
> >> http://zope.org/Members/adytumsolutions/HowToLoveZODB_PartI
> >
> > As per:
> > http://zope.org/Members/adytumsolutions/HowToLoveZODB_PartII/
> > HowToLoveZODB_PartIII
> >
> >     If we hadn't based our schema on the Persistent class, we would  
> > need to
> >     add an extra line of code:
> >
> >>>> get_transaction().commit()
> >
> >     which would write the data to the database by using the commit
> >     command. However, since we did use Persistent, commits are done
> >     automatically for us.
> >
> > Either I'm confused by the text, or this is incorrect (or both!) :-)
> 
> Thanks! Yeah, that's what I had thought... I was experimenting today,  
> though and didn't use the commit and it looked like I got back the new  
> data... I must have misread it, though.
> 
> Fixing the text now... ;-)
> 
> d
> 
> 
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
> 
> ZODB-Dev mailing list  -  ZODB-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zodb-dev
>