Differences between revisions 11 and 13 (spanning 2 versions)
Revision 11 as of 2007-07-11 15:57:35
Size: 1539
Editor: sladen
Comment: Note that the mailing list is open, even if the archives aren't...
Revision 13 as of 2007-07-12 05:47:01
Size: 2388
Editor: niemeyer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:

== Highlights ==

 * Designed from day one to be database administrator friendly.
 * Storm does not dictate your datamodel.
 * Designed from day one to work both at the low end, with trivial small
 databases, and the high end, with applications accessing billion row tables
 and committing to multiple database backends.
 * Clean and lightweight API offers a short learning curve and long-term
 maintainability.
 * Designed from day one to work both with thin relational databases, such
 as SQLite, and big iron systems like PostgreSQL, DB2 & Oracle.
 * Distributed database integrity using two-phase commit (if your Python
 driver and database backend support it).
 * Storm lets you efficiently access and update large datasets by allowing
 you to formulate complex queries spanning multiple tables using Python.
 * Storm allows you to fallback to SQL if needed (or if you just prefer),
 allowing you to mix 'old school' code and ORM code
Line 15: Line 33:
 * [:Install] ## * [:Install]
Line 30: Line 48:

  /!\ ''Note: viewing the mailing list archives currently requires signing up to the mailing list first!).''

What is Storm?

Storm is an object-relational mapper (ORM) for Python developed at Canonical. The project has been in development for more than a year for use in Canonical projects such as [https://launchpad.net Launchpad], and has recently been released as an open-source product.

Highlights

  • Designed from day one to be database administrator friendly.
  • Storm does not dictate your datamodel.
  • Designed from day one to work both at the low end, with trivial small databases, and the high end, with applications accessing billion row tables and committing to multiple database backends.
  • Clean and lightweight API offers a short learning curve and long-term maintainability.
  • Designed from day one to work both with thin relational databases, such

    as SQLite, and big iron systems like PostgreSQL, DB2 & Oracle.

  • Distributed database integrity using two-phase commit (if your Python driver and database backend support it).
  • Storm lets you efficiently access and update large datasets by allowing you to formulate complex queries spanning multiple tables using Python.
  • Storm allows you to fallback to SQL if needed (or if you just prefer), allowing you to mix 'old school' code and ORM code

Documentation

There's a [:Tutorial: tutorial] available. More documentation will come in the near future. Questions are welcome in the mailing list.

  • [:Dependencies: Dependencies/Requirements]

License

Storm is licensed under the [http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html LGPL 2.1].

Community

The Storm mailing list is publicly available at:

There is also a #storm IRC channel on irc.freenode.net; stop by and chat!

Development

Development of Storm may be tracked in Launchpad:

The source code may be obtained using [http://bazaar-vcs.org Bazaar]:

  • bzr branch http://bazaar.launchpad.net/~storm/storm/trunk

Code may be browsed at:

Download

You can find released files at:

FrontPage (last edited 2024-10-08 09:38:41 by ranman)