Next | Query returned 5 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2014-06-01 14:49:35 by Thomas Klausner | Files touched by this commit (208)
Log message:
Remove FETCH_USING.
It is a user-defined variable and should NOT be set in Makefiles.
   2013-12-05 10:38:10 by ndb | Files touched by this commit (3)
Log message:
only https fetch possible anymore.
   2012-10-07 15:57:25 by Aleksej Saushev | Files touched by this commit (211)
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
Mark packages that don't or might probably not have staged installation.
   2010-05-08 00:41:52 by Kamel Derouiche | Files touched by this commit (3) | Package updated
Log message:

	wip-change:
	----------
	o update package
	o add documentation (README) file
   2009-07-18 23:12:50 by Thomas Klausner | Files touched by this commit (4) | Imported package
Log message:
Initial import of py-storm-0.14:

Storm is an Object Relational Mapper for Python.

    * 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.


Next | Query returned 5 messages, browsing 1 to 10 | previous