Differences between revisions 3 and 4
Revision 3 as of 2008-06-19 17:42:21
Size: 3733
Editor: localhost
Comment: converted to 1.6 markup
Revision 4 as of 2008-09-23 03:24:48
Size: 21
Editor: jamesh
Comment: Redirect to front page rather than duplicating content.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== 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 ==

'''Design'''

 * Clean and lightweight API offers a short learning curve and long-term
 maintainability.
 * Storm is developed in a test-driven manner. An untested line of code is
 considered a bug.
 * Storm needs no special class constructors, nor imperative base classes.
 * Storm is well designed (different classes have very clear boundaries,
 with small and clean public APIs).
 * Designed from day one to work both with thin relational databases, such
 as SQLite, and big iron systems like PostgreSQL and MySQL.
 * Storm is easy to debug, since its code is written with a KISS principle,
 and thus is easy to understand.
 * 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.
 * It's very easy to write and support backends for Storm (current backends
 have around 100 lines of code).

'''Features'''

 * Storm is fast.
 * 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
 * Storm handles composed primary keys with ease (no need for surrogate keys).
 * Storm doesn't do schema management, and as a result you're free to
 manage the schema as wanted, and creating classes that work with Storm
 is clean and simple.
 * Storm works very well connecting to several databases and using the
 same Python types (or different ones) with all of them.
 * Storm can handle obj.attr = <A SQL expression> assignments, when
 that's really needed (the expression is executed at INSERT/UPDATE
 time).
 * Storm handles relationships between objects even before they were
 added to a database.
 * Storm works well with existing database schemas.
 * Storm will flush changes to the database automatically when needed, so
 that queries made affect recently modified objects.


== Documentation ==

There's a [[Tutorial| tutorial]] available. We are always working on improving the documentation. Questions are welcome in the mailing list.

 * [[Tutorial]] (based on code in trunk)
 * [[Manual]] (under construction)
 * [[http://twistedmatrix.com/users/radix/storm-api/|API docs]]
 * Web Framework Integration
   * [[http://divmod.org/trac/wiki/DivmodNevow/Storm|Nevow/Twisted]] (forthcoming)

== License ==

Storm is licensed under the [[http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html|LGPL 2.1]]. Contributions must have copyright assigned to Canonical.

== Community ==

The Storm mailing list is publicly available at:

  https://lists.canonical.com/mailman/listinfo/storm

There is also a #storm IRC channel on irc.freenode.net; stop by and chat! We have
a PublishBot up and running.

== Development ==

Development of Storm may be tracked in Launchpad:

  https://launchpad.net/storm

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:

  http://codebrowse.launchpad.net/~storm/storm/trunk/files

If you want to contribute, please see DevelopmentProcedure.


== Download ==

You can find released files at:

  https://launchpad.net/storm/+download
#REDIRECT FrontPage

Начало (last edited 2008-09-23 03:24:48 by jamesh)