[Checkins] SVN: zc.catalog/trunk/ Move changes down.
Stephan Richter
srichter at cosmos.phy.tufts.edu
Sat Nov 3 14:32:43 EDT 2007
Log message for revision 81443:
Move changes down.
Changed:
A zc.catalog/trunk/CHANGES.txt
U zc.catalog/trunk/setup.py
D zc.catalog/trunk/src/zc/catalog/CHANGES.txt
-=-
Copied: zc.catalog/trunk/CHANGES.txt (from rev 81442, zc.catalog/trunk/src/zc/catalog/CHANGES.txt)
===================================================================
--- zc.catalog/trunk/CHANGES.txt (rev 0)
+++ zc.catalog/trunk/CHANGES.txt 2007-11-03 18:32:42 UTC (rev 81443)
@@ -0,0 +1,99 @@
+==================
+zc.catalog changes
+==================
+
+The 1.2 line supports Zope 3.4/ZODB 3.8. The 1.1 line supports Zope
+3.3/ZODB 3.7.
+
+1.2.0 (2007-11-03)
+------------------
+
+Features added
+~~~~~~~~~~~~~~
+
+* Updated package meta-data.
+
+* zc.catalog now can use 64-bit BTrees ("L") as provided by ZODB 3.8.
+
+* Albertas Agejavas (alga at pov.lt) included the new CallableWrapper, for
+ when the typical Zope 3 index-by-adapter story
+ (zope.app.catalog.attribute) is unnecessary trouble, and you just want
+ to use a callable. See callablewrapper.txt. This can also be used for
+ other indexes based on the zope.index interfaces.
+
+* Extents now have a __len__. The current implementation defers to the
+ standard BTree len implementation, and shares its performance
+ characteristics: it needs to wake up all of the buckets, but if all of the
+ buckets are awake it is a fairly quick operation.
+
+* A simple ISelfPoulatingExtent was added to the extentcatalog module for
+ which populating is a no-op. This is directly useful for catalogs that
+ are used as implementation details of a component, in which objects are
+ indexed explicitly by your own calls rather than by the usual subscribers.
+ It is also potentially slightly useful as a base for other self-populating
+ extents.
+
+
+1.1.1 (2007-3-17)
+-----------------
+
+Bugs fixed
+~~~~~~~~~~
+
+'all_of' would return all results when one of the values had no results.
+Reported, with test and fix provided, by Nando Quintana.
+
+
+1.1 (2007-01-06)
+----------------
+
+Features removed
+~~~~~~~~~~~~~~~~
+
+The queueing of events in the extent catalog has been entirely removed.
+Subtransactions caused significant problems to the code introduced in 1.0.
+Other solutions also have significant problems, and the win of this kind
+of queueing is qustionable. Here is a run down of the approaches rejected
+for getting the queueing to work:
+
+* _p_invalidate (used in 1.0). Not really designed for use within a
+ transaction, and reverts to last savepoint, rather than the beginning of
+ the transaction. Could monkeypatch savepoints to iterate over
+ precommit transaction hooks but that just smells too bad.
+
+* _p_resolveConflict. Requires application software to exist in ZEO and
+ even ZRS installations, which is counter to our software deployment goals.
+ Also causes useless repeated writes of empty queue to database, but that's
+ not the showstopper.
+
+* vague hand-wavy ideas for separate storages or transaction managers for the
+ queue. Never panned out in discussion.
+
+
+1.0 (2007-01-05)
+----------------
+
+Bugs fixed
+~~~~~~~~~~
+
+* adjusted extentcatalog tests to trigger (and discuss and test) the queueing
+ behavior.
+
+* fixed problem with excessive conflict errors due to queueing code.
+
+* updated stemming to work with newest version of TextIndexNG's extensions.
+
+* omitted stemming test when TextIndexNG's extensions are unavailable, so
+ tests pass without it. Since TextIndexNG's extensions are optional, this
+ seems reasonable.
+
+* removed use of zapi in extentcatalog.
+
+
+0.2 (2006-11-22)
+----------------
+
+Features added
+~~~~~~~~~~~~~~
+
+* First release on Cheeseshop.
Modified: zc.catalog/trunk/setup.py
===================================================================
--- zc.catalog/trunk/setup.py 2007-11-03 18:31:51 UTC (rev 81442)
+++ zc.catalog/trunk/setup.py 2007-11-03 18:32:42 UTC (rev 81443)
@@ -49,8 +49,8 @@
read('src', 'zc', 'catalog', 'callablewrapper.txt')
+ '\n\n' +
read('src', 'zc', 'catalog', 'browser', 'README.txt')
- #+ '\n\n' +
- #read('CHANGES.txt')
+ + '\n\n' +
+ read('CHANGES.txt')
),
keywords = "zope3 i18n date time duration",
classifiers = [
Deleted: zc.catalog/trunk/src/zc/catalog/CHANGES.txt
===================================================================
--- zc.catalog/trunk/src/zc/catalog/CHANGES.txt 2007-11-03 18:31:51 UTC (rev 81442)
+++ zc.catalog/trunk/src/zc/catalog/CHANGES.txt 2007-11-03 18:32:42 UTC (rev 81443)
@@ -1,99 +0,0 @@
-==================
-zc.catalog changes
-==================
-
-The 1.2 line supports Zope 3.4/ZODB 3.8. The 1.1 line supports Zope
-3.3/ZODB 3.7.
-
-1.2.0 (2007-11-03)
-------------------
-
-Features added
-~~~~~~~~~~~~~~
-
-* Updated package meta-data.
-
-* zc.catalog now can use 64-bit BTrees ("L") as provided by ZODB 3.8.
-
-* Albertas Agejavas (alga at pov.lt) included the new CallableWrapper, for
- when the typical Zope 3 index-by-adapter story
- (zope.app.catalog.attribute) is unnecessary trouble, and you just want
- to use a callable. See callablewrapper.txt. This can also be used for
- other indexes based on the zope.index interfaces.
-
-* Extents now have a __len__. The current implementation defers to the
- standard BTree len implementation, and shares its performance
- characteristics: it needs to wake up all of the buckets, but if all of the
- buckets are awake it is a fairly quick operation.
-
-* A simple ISelfPoulatingExtent was added to the extentcatalog module for
- which populating is a no-op. This is directly useful for catalogs that
- are used as implementation details of a component, in which objects are
- indexed explicitly by your own calls rather than by the usual subscribers.
- It is also potentially slightly useful as a base for other self-populating
- extents.
-
-
-1.1.1 (2007-3-17)
------------------
-
-Bugs fixed
-~~~~~~~~~~
-
-'all_of' would return all results when one of the values had no results.
-Reported, with test and fix provided, by Nando Quintana.
-
-
-1.1 (2007-01-06)
-----------------
-
-Features removed
-~~~~~~~~~~~~~~~~
-
-The queueing of events in the extent catalog has been entirely removed.
-Subtransactions caused significant problems to the code introduced in 1.0.
-Other solutions also have significant problems, and the win of this kind
-of queueing is qustionable. Here is a run down of the approaches rejected
-for getting the queueing to work:
-
-* _p_invalidate (used in 1.0). Not really designed for use within a
- transaction, and reverts to last savepoint, rather than the beginning of
- the transaction. Could monkeypatch savepoints to iterate over
- precommit transaction hooks but that just smells too bad.
-
-* _p_resolveConflict. Requires application software to exist in ZEO and
- even ZRS installations, which is counter to our software deployment goals.
- Also causes useless repeated writes of empty queue to database, but that's
- not the showstopper.
-
-* vague hand-wavy ideas for separate storages or transaction managers for the
- queue. Never panned out in discussion.
-
-
-1.0 (2007-01-05)
-----------------
-
-Bugs fixed
-~~~~~~~~~~
-
-* adjusted extentcatalog tests to trigger (and discuss and test) the queueing
- behavior.
-
-* fixed problem with excessive conflict errors due to queueing code.
-
-* updated stemming to work with newest version of TextIndexNG's extensions.
-
-* omitted stemming test when TextIndexNG's extensions are unavailable, so
- tests pass without it. Since TextIndexNG's extensions are optional, this
- seems reasonable.
-
-* removed use of zapi in extentcatalog.
-
-
-0.2 (2006-11-22)
-----------------
-
-Features added
-~~~~~~~~~~~~~~
-
-* First release on Cheeseshop.
More information about the Checkins
mailing list