On behalf of all Storm developers, I'm glad to announce that the 0.14
release is out and ready for consumption.
Download information and documentation may be found at the web site:
https://storm.canonical.com/
This release brings the long-awaited storm.django package, to use Storm
in Django applications. It also offers some interesting performance
enhancements, one with the interaction with the Zope transaction
manager, the other dealing with a bottleneck in the Store.flush method.
Thanks to all contributors and users that helped make this release!
Here is the full changelog:
Improvements
------------
- A new doctest describing the 'Infoheritance' pattern is integrated
into the test suite.
- A new storm.django package has been added to allow use of Storm
within Django applications.
- The way Storm interacts with the Zope transaction manager has
changed. Rather than using a synchronizer to join each new
transaction, it now delays joining the transaction until the store
is actually used.
- The Store constructor takes an optional cache keyword argument.
- ResultSets now offer an is_empty() method.
Bug fixes
---------
- Manage better row full of NULL in case of LEFT JOIN, without
validating against object constraints.
- The Reference class now has an __ne__() method, so inequality
checks against a reference now work in find expressions (bug
#244768 reported by Stuart Bishop).
- Make ResultSet.count() handles the distinct, limit and offset flags,
toreally reflect the length of the current ResultSet.
- The store doesn't iterate on all the alive objects anymore, using
insteadevents that objects can subscribe to. This improves
performance drastically when lots of objects are in the cache.
--
Thomas
--
storm mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/storm
