[ZODB-Dev] Re: I want Object Gadfly

[Aaron Watters]

Hi Jim and others.

Thanks for the interesting comment!

I'm pretty sure this is not what Jim has in mind, but I have
been messing around with a sort of hybrid relational/object
database system which may eventually become a backend
for a gadfly based front end.

Currently it has nothing to do with oql and little to do with
sql. It's designed to provide transactions with concurrency
control and recovery in the ways that I have found need for
over the years. I have a prototype that I am putting in
mothballs for a complete rewrite. If someone wants to have
a look I'll send a zip file (you'll need stackless python, and
it has no real documentation).

I'm basing it in stackless because stackless
python makes it very easy
to suspend a transaction waiting for a resource to be released,
for example.

Thanks again! -- Aaron Watters

Jim Fulton wrote:

>
> I've been thinking a lot recently about relationships, relations,
> and associations. I'm coming to the conclusions that:
>
> - There should be two separate concepts:
>
> - Relations, which model externally imposed relationships
> between objects.
>
> - Accociations, which model direct relationships between objects
> You should be able to access associations directly through objects
> without accessing some service. Maybe there are two kinds of these:
> simple and "content" (for lack of a better term)> Simple associations
> are just Python references. Content associations are themselves content.
> They may have hub ids, can be cataloged. Maybe they can even show up in
> relations.
>
> - Relations should be implemented via Object Gadfly (or something
> like it). Object Gadfly is Gadfly implemented over ZODB. It
> allows you to use SQL (and presumably other sorts of analysis)
> against relations (tables) stored in the ZODB. These relations
> can contain any objects.
>
> With Object Gadfly, you can create relations between objects using
> content-space tables or named site-wide utilities. Data can be added
> to them explicitly, or automatically via event subscription. Tables can
> be indexed and you can execute automatically optimized queries against
> them using SQL.
>
> Unfortunately, Object Gadfly doesn't exist. :(
> Any takers? :)
>
> Notes:
>
> . Despite references to Zope concepts like
> hubs, content and utilities, Object Gadfly need have
> nothing to do with Zope.
>
> Object Gadfly need not be ZODB specific.
> It only needs to have an open enough storage model to allow
> ZODB to be plugged in.
>
>
> Jim
>