[storm] use storm from existing db-scheme

[James Henstridge]

On 27/03/2008, Vsevolod Balashov <vsevolod at balashov.name> wrote:
>  Storm is cool! Please don't waste it in future.
>
>  I`m think "waste" is:
>
>  - zope (i`m sorry, frameworks support must be in separate packages, like
>  my middlestorm)
>  - python code for schema creation (instead pure SQL)
>  - python code for trigger emulation (like SQLAlchemy or ActiveRecord bad
>  practice)
>
>  ORM is a ORM. No more. IMHO.

I think there are cases where integration with parts of Zope make a
lot of sense.

One of the design goals for Storm was to make it easy to talk to
multiple databases at once.  The place where that support falls down
at the moment is that you can't coordinate the transactions of those
stores: this requires two-phase commit.

Even if we expose 2PC through Storm's Store API, we'll still need a
transaction manager to coordinate things.  I think it makes most sense
to default to Zope's transaction module (which can be installed
independently) here, rather than implementing our own.

This would not preclude integration with transaction managers from
other frameworks since they could use the same Store APIs that the
zope transaction manager glue uses.  It would mean that we'd have a
working 2PC story for use in all other cases though.

James.