Re: Applause for ZODB! And a question: How do you get pending change info from a transaction object?

I have not spent much time looking at Newt DB beyond a quick glance.

Since what I am starting is a completely new project, I want to use the 
latest and greatest approach and technology choices for this (ZODB) 
paradigm to ensure better compatibility with the future. It looks like Newt 
DB with the RelStorage Postgres backend embodies your latest vision and 
thrust going forward, am I correct? And with Postgres as the fundamental 
basis of storage, it would be more palatable to the industry in conformity 
to their "good practice" (sells better). Thus, for a completely new project 
that does not need to worry about being bullet proof for enterprise 
production (bleeding edge is safe for me), am I correct to assume that your 
recommendation would be to jump head first into Newt DB instead of 
traditional ZODB?

The overall application development interface/experience/workflow is pretty 
much the same, right? (After setting up the environment and low level 
development details.) Is it somewhat accurate to say that Newt DB is the 
next generation of ZODB?

Many thanks,
David

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.