Re: Schevo/ZODB integration roadmap

On Thu, Feb 9, 2017 at 11:27 AM, Etienne Robillard <[email protected]>
wrote:

> Hi Jim,
> Le 2017-02-09 à 10:54, Jim Fulton a écrit :
>
>
>
> On Thu, Feb 9, 2017 at 10:34 AM, Etienne Robillard <[email protected]>
> wrote:
>
>> I think I will need to upgrade the ZODB backend to use ZEO... I have
>> locking issues attempting to use FileStorage with multiple processes.
>
>
> I'm puzzled that Schevo is so closely coupled to ZODB. I don't know what
> Schevo is and I've been unable to find documentation.
>
> Here's some relevant documentation for Schevo:
>
> http://www.isotopesoftware.ca/documentation/libschevo/
> http://www.isotopesoftware.ca/documentation/libschevo/
> design/structures.html
>


Too bad that  doesn't say what problem Schevo is trying to solve. (Perhaps
I could infer it if I worked hard.) /me throws stones from glass house.

If Schevo somehow imposes Schemas on objects (ROM?), as Chris suggests, I
> don't understand why it has to interact with persistence at all. Over the
> years, many such systems have been built within the Zope community and
> AFAIK, none of them interacted directly with ZODB.
>
> I think Schevo was initially designed as a object relational database
> management system (ORDBMS)
> on top of Durus.
>

But Durus isn't an RDBMS either and it already defines an object api.



> However, since Schevo is not tightly integrated to Durus, it is possible
> to use the ZODB backend to make transactions and process a BTree.
>

So is the issue which flavor of persistence is used?  That I could
understand.  But then I still don't understand why the back end should
matter.

Jim

-- 
Jim Fulton
http://jimfulton.info

-- 
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.