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 (in my opinion). 1 >>> class Employee(Person): 2 ... __storm_table__ = "employee" 3 ... company_id = Int() 4 ... company = Reference(company_id, Company.id) Here we see that I have to declare a company_id and the the foreign key - Django does this in one step with ForeignKey(Model). It just seems that Django's ORM is already syntactically nicer and, other than inheritance, Storm doesn't seem to have any really compelling feature. On 7/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > 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 already has, and looks to be > behind SQLAlchemy which people are already working on integrating in > some fashion (maybe). > > > -Doug > > > > > -- www.PovertyFighters.com If you knew you could fight hunger and poverty, conserve the environment, empower women, combat AIDS, improve labor standards and win a national competition for your university--all with only two clicks a day--would you do it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
