On Jul 11, 7:50 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote: > So, in that spirit, I haven't had time to investigate Storm in the way > that I would like. Can anybody provide a list of actual technical > advantages that it has over it's competitors like SQLAlchemy and > DejaVu?
I'd like to see that as well, but a cursory glance seems to show that Storm has a slightly different focus than either of the others. ORM's in general tend to fall into three distinct camps: 1. those that work with relational sets 2. those that work with "objects", and 3. those that implement the latter on top of the former. Dejavu 1.5, for example, does objects, but Dejavu 2.0 will do objects on top of the newly-broken-out Geniusql 1.0 which works with relational sets. SQLAlchemy is mostly set-oriented, with libraries like Elixir doing objects on top of it. Storm seems to be objects only, leaving set-based queries and commands to an execute(sql) call. Having a true relational layer provides expressive power that an object-only layer cannot provide; that will be the largest determinant of "technical advantage". If you only care about objects (i.e. for classic OLTP work only), then we can squabble about API design and other bikesheds until the cows come home. ;) Robert Brewer System Architect Amor Ministries [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
