[storm] Django & Storm

[James Henstridge]

On Thu, Jan 8, 2009 at 2:36 AM, Eduardo Willians <edujurista at gmail.com> wrote:
> Please don't judge me bad for this email, that's just my ponit-of-view.
>
> We know James Henstridge is already working on the integration between
> Storm and Django, that's awesome (and my wish of long time).
>
> My point, however, is that Storm team should dedicate a little more
> attention to this project: Storm future success may depend on it.
> Let's see.
>
> Most (or all) of us here consider Storm the best ORM for Python. It's
> clearly for us how robust is Storm code and the most consistent OO
> tool. That's ok, but our community is still incipient (IMHO), and
> given that open projects are sustained by communites, Storm will rise
> as the 'de facto' option if we draw more attention to it. And even if
> Storm is better designed (as I really think), I'm concerned about
> Storm's future.
>
> Then, given that Django is becoming more and more important, a good
> idea for us is advance toward the integration with it, so this will
> give developers an excellent integrated ORM that works nice on
> intranet and internet, and (finally) bringing a stronger community for
> Storm.

So, with 0.14 released we have basic Django support in Storm.  This
gives you the basic ability to access the database with both Storm and
the Django ORM through the same connection (provided you only access
each table with one ORM) and transaction manager integration to allow
access to additional databases from Storm.

This is essentially the bare minimum you need to build a Django
application with Storm.  There is definitely more work to do, but the
question is what additional features are people looking for?  I gather
you probably have some suggestions, so recording them as bug reports
would be helpful.

Some things that have been brought up before include:

1. integration with Django's admin app.  I took a quick look at what
would be required here a while ago but gave up.  The
django.contrib.admin code is pretty heavily tied to Django's ORM, so
this would probably require someone with a bit more knowledge of the
code than me.

2. An equivalent of Reference / ReferenceSet linking from a Storm
class to a Django class.  As both Storm and Django cache row data,
using both ORMs to access a single table is likely to cause problems.
If you are trying to integrate with existing Django code (e.g.
django.contrib.auth), you probably have relationships with Django
managed tables.  It would be nice if those relationships were as easy
to work with as those between Storm managed tables where possible.

3. <your feature here>
...


James.