This really isn't meant to compete with Django, more with SQLAlchemy.
So far it seems like it's main competing feature is handling
multiple-databases easily and joining across them.
Damien Gassart saw these posts on digg, made by zzzeek and niemeyer,
the SQLAlchemy and Storm lead developers, res
Ya some of the stuff seems like a bit of extra work. I really like how
they handle the objects in memory though so they're referencable
before saving in the database, even with ForeignKeys. Although our
Django is patched, the current trunk doesn't even store multiple
references to the same object
It's also just very verbose.
1 >>> class Person(object):
2 ... __storm_table__ = "person"
3 ... id = Int(primary=True)
4 ... name = Unicode()
So, I have to declare a __storm_table__ and id for every model. That should
be assumed by default and allowed to be overwritten (i
On Jul 10, 4:43 pm, David Cramer <[EMAIL PROTECTED]> wrote:
> Not sure if you guys have seen this, but maybe Django can take a bit
> from what it does well.
>
> https://storm.canonical.com/Tutorial
The problem is no one knows what it 'does well' yet :-)
It is missing many of the features Django
