Re: [Zope-dev] ZCatalog Lazy Results

2001-02-22 Thread Johan Carlsson
Casey Duncan [EMAIL PROTECTED] wrote: Yes, you always get all the meta-data. However, does anyone know how the "used" argument of ZCatalog.searchResults works, or why you would use it? 'used' tells you the names of the indexes which actually participated in the search (as distinct

Re: [Zope-dev] ZCatalog Lazy Results

2001-02-22 Thread Tres Seaver
On Thu, 22 Feb 2001, Johan Carlsson wrote: Casey Duncan [EMAIL PROTECTED] wrote: Yes, you always get all the meta-data. However, does anyone know how the "used" argument of ZCatalog.searchResults works, or why you would use it? 'used' tells you the names of the indexes which

Re: [Zope-dev] ZCatalog Lazy Results

2001-02-22 Thread Dieter Maurer
Tres Seaver writes: 'getObject' forces you to "wake up" the catalogued object; in a large enough result set, the price is pretty punitive, compared to serving the results as cached metadata. You can batch large result sets: "getObject" would just be applied to the objects in the batch. The

Re: [Zope-dev] ZCatalog Lazy Results

2001-02-20 Thread Casey Duncan
--- Johan Carlsson [EMAIL PROTECTED] wrote: Hi, I need to check an assumption I have made on the ZCatalog Brains and Lazy Results from reading the source. 1. The Brains gets its schema from the ZCatalog and this schema is basicly fixed. E.g. a search result always has the

Re: [Zope-dev] ZCatalog Lazy Results

2001-02-20 Thread Johan Carlsson
I would rather be able to construct a Brain Schema at search time equivalent to the way theSELECT statement sets up the result attributes in SQL. Example: resultset = Catalog.searchResults(query,schema=('id','title','keywords')) Why is this important? I would

Re: [Zope-dev] ZCatalog Lazy Results

2001-02-20 Thread Johan Carlsson
How many is "a lot" of meta datas? At least 20-30. Johan Catalog.searchResults(query,schema=('id','title','keywords')) Why is this important? I would suggest not putting big stuff in the meta-data that might warrant this. Just use the nifty new (v2.3) getObject