On Mon, May 09, 2005 at 05:28:05PM +0200, Thomas Guettler wrote:
> > > Since btrees and btree ranges don't know their size, you need to do
> > > something like this:
> > > - do range searches at the end
> > > - if index "foo" is used, use it first, ...
> >
> > Hmmm. Can you elaborate on this? I don
Am Donnerstag, 5. Mai 2005 19:18 schrieb Christian Robottom Reis:
> On Tue, May 03, 2005 at 02:44:58PM +0200, Thomas Guettler wrote:
> > It would be better if the index would do the search for customer_id
> > first, and then filter the result by deleting entries which are not in
> > the given time
On Tue, May 03, 2005 at 02:44:58PM +0200, Thomas Guettler wrote:
> It would be better if the index would do the search for customer_id
> first, and then filter the result by deleting entries which are not in
> the given time period.
>
> Has anyone done such a "Query Optimization"? (Zope, Zope3, In
Thomas Guettler wrote at 2005-5-3 14:44 +0200:
> ...
>I developed a simple index using ZODB. Searching for single values is
>very fast. Searching big ranges is slow.
>
>Example:
>Search:
>
>customer_id=0815
>date_start=2001-01-01
>date_end=2004-12-31
>
>The index holds a btree which maps valu
[Thomas Guettler]
> I developed a simple index using ZODB. Searching for single values is
> very fast. Searching big ranges is slow.
>
> Example: Search:
>
> customer_id=0815
> date_start=2001-01-01
> date_end=2004-12-31
>
> The index holds a btree which maps values to docids. The search for
> cust