[Zope-Checkins] CVS: Zope/lib/python/Products/ZCatalog - IZCatalog.py:1.4.2.2

Casey Duncan casey@zope.com
Tue, 10 Dec 2002 11:05:56 -0500


Update of /cvs-repository/Zope/lib/python/Products/ZCatalog
In directory cvs.zope.org:/tmp/cvs-serv32693

Modified Files:
      Tag: Zope-2_6-branch
	IZCatalog.py 
Log Message:
Remove "search" method from ZCatalog interfaces that was removed in the backport


=== Zope/lib/python/Products/ZCatalog/IZCatalog.py 1.4.2.1 => 1.4.2.2 ===
--- Zope/lib/python/Products/ZCatalog/IZCatalog.py:1.4.2.1	Tue Dec 10 10:55:00 2002
+++ Zope/lib/python/Products/ZCatalog/IZCatalog.py	Tue Dec 10 11:05:55 2002
@@ -163,8 +163,8 @@
           Default behavior is to sort ascending.
           
           sort_limit -- An optimization hint to tell the catalog how many
-          results you are really interested in. See the limit argument
-          to the search method for more details.
+          results you are really interested in. Results in faster queries
+          that use less memory.
 
         There are some rules to consider when querying this method:
 
@@ -197,29 +197,4 @@
         """Search the catalog, the same way as 'searchResults'.
         """
         
-    def search(query_request, sort_index=None, reverse=0, limit=None, merge=1):
-        """Programmatic search interface, use for searching the catalog from
-        scripts.
-            
-        query_request -- Dictionary containing catalog query. This uses the 
-        same format as searchResults.
-        
-        sort_index -- Name of sort index
-        
-        reverse -- Boolean, reverse sort order (defaults to false)
-        
-        limit -- Limit sorted result count to the n best records. This is an
-        optimization hint used in conjunction with a sort_index. If possible
-        ZCatalog will use a different sort algorithm that uses much less memory
-        and scales better then a full sort. The actual number of records
-        returned is not guaranteed to be <= limit. You still need to apply the
-        same batching to the results. Since the len() of the results will no 
-        longer be the actual result count, you can use the
-        "actual_result_count" attribute of the lazy result object instead to
-        determine the size of the full result set.
-
-        merge -- Return merged, lazy results (like searchResults) or raw 
-        results for later merging. This can be used to perform multiple
-        queries (even across catalogs) and merge and sort the combined results.
-        """
 __doc__ = IZCatalog.__doc__ + __doc__