I've seen this mentioned a couple times (and saw the aforementioned
slashdot post as well).
My impression is that Storm is to SQLAlchemy as Django's ORM is to
SQLObject. It's well-defined and polished, and, for what it's worth,
production-ready, but some design decisions that come from it being a
relatively proprietary and internal project may limit its community
acceptance.
There are a couple things that I really like. It can do composite
primary keys, and the use of __variables__ to set database metadata on
a class seems quite Pythonic. It's also less verbose than SQLAlchemy,
and seems to do most of its data mapping through inference (also
Pythonic).
Storm doesn't seem to contain any primary functionality for database
creation, which can be either good or bad, depending on your point of
view. For some, this is a deal breaker, as SQL is a world of strange
and incompatible implementation-specific syntax; but for others ddl is
a task best left to ddl, not reimplemented in an ORM.
Still, things that bother me the most about Storm is how quickly the
tutorial dropped down into SQLesque syntax:
>>> ruy.name = SQL("(SELECT name || ' Ritcher' FROM person WHERE
id=4)")
I'm also frustrated by the "me too" sense that I get from the project.
I realize that Storm was developed internally by Canonical at a time
before the likes of SQLAlchemy, and that Canonical is doing no
disservice by releasing this code to the community, but I'd rather see
these (and other) projects continue to meld together, rather than
continue duplicating work for the sake of a slightly different
interface. If we're not careful, Python might soon have more ORM's
than even web frameworks!
~jon
On Jul 10, 10:30 pm, Dakila <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Just found out at slashdot, might be of interest to you.
> Canonical Begins To Open-Source
> Launchpadhttp://linux.slashdot.org/linux/07/07/10/1736238.shtmlhttps://storm.canonical.com/Tutorial
>
> "Storm is an ORM that simplifies the development of database-backed
> applications in Python, especially for projects that use very large
> databases or multiple databases with a seamless web front-end", said
> Gustavo Niemeyer, lead developer of Storm at Canonical. "Storm is
> particularly designed to feel very natural to Python programmers, and
> exposes multiple databases as /stores/ in a clean and easy to use
> fashion."
>
> I wonder how it compares with SQLAlchemy or SQLObject.
>
> Dakila
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to turbogears@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
