Correction: the doc order is fine. My test was based on the existing
'TestMultiSearcher', and I hadn't noticed the swapping of the index order
here:
// VITAL STEP:adding the searcher for the empty index first, before
the searcher for the populated index
searchers[0] = new IndexSear
Hi,
I have a postgresql table which expects to have around 20 millions rows.
- The structure is the following;
code int -- can take one of 100 values
property varchar(250) -- can take one of 5000 values
param01 char(10) -- can take one of 10 values
param02 char(10) -- can
Chris Hostetter <[EMAIL PROTECTED]> wrote on 12/04/2006 01:41:37 AM:
> : them in one field). One of the problems I see would be with values
that
> : over lap (Example, name where one name is Jason Bateman, and one is
Jason
> : Bateman Black, and it would be hard to replicate the Discrete Search
fo
