AW: UdmCheckIndex bug?

Thanks! Now it works.

The problem was that I was building the index still with 3.2 but querying with 3.3.

Kind regards
Matthias


> -----Ursprüngliche Nachricht-----
> Von: Alexander Barkov [mailto:[email protected]]
> Gesendet: Dienstag, 23. November 2010 16:35
> An: Matthias Pigulla
> Cc: [email protected]
> Betreff: Re: UdmCheckIndex bug?
> 
> Hi Matthias,
> 
> Matthias Pigulla wrote:
> >
> > Dear all,
> >
> > I've got a problem with mnogosearch 3.3.8 that was not present in
> 3.2.
> >
> > First: The CVS access stated on the mnoGoSearch website seems to be
> > wrong/not working anymore. Is there any way to review file histories?
> >
> > The problem itself seems to come from UdmCheckIndex in src/sql.c. To
> me
> > it seems that a particular query yields no results, so
> > UdmBlobReadTimestamp works (no query error) but returns the default
> > value, which is 0 in UdbCheckIndex. This in turn leads to the error
> > message ("Inverted word index not found..."), which is wrong (the
> index
> > is there).
> >
> > Is this a bug or am I missing something?
> 
> Please try
> 
> SELECT word FROM bdict WHERE word LIKE '#%';
> 
> 
> Its output should look like this:
> 
> +----------------+
> | word           |
> +----------------+
> | #last_mod_time |
> | #rec_id        |
> | #site_id       |
> | #ts            |
> | #version       |  <-- this record is important
> +----------------+
> 
> If you don't have the '#version' record, then
> you need to run 'indexer -Eblob' with the new indexer.
> 
> 
> 
> >
> > Kind regards
> > Matthias
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]