Re: 3.23.31 gives FULLTEXT problems on sparc64 Linux

2001-02-05 Thread Tibor Simko
Hello > > The error says: "Can't read indexpage from filepos: -1". [...] > > Thank you for reporting this. This will be fixed in a next release. > But it was really not a big problem - the table was not really > corrupted. [...] Thanks for the fix and the explanation! cheers -- TS -

Re: 3.23.31 gives FULLTEXT problems on sparc64 Linux

2001-01-27 Thread Sergei Golubchik
Hi! Sorry for delay :-( On Jan 24, Tibor Simko wrote: > Hello > > I wrote: > > > > After upgrading to 3.23.31, FULLTEXT selects give often "error -1 > > > from table handler" for me. [...] > > Sergei Golubchik <[EMAIL PROTECTED]> wrote: > > > Thanks for a bug report! This would be fixed in

Re: 3.23.31 gives FULLTEXT problems on sparc64 Linux

2001-01-24 Thread Tibor Simko
Hello I wrote: > > After upgrading to 3.23.31, FULLTEXT selects give often "error -1 > > from table handler" for me. [...] Sergei Golubchik <[EMAIL PROTECTED]> wrote: > Thanks for a bug report! This would be fixed in a nex release. Thanks. In 3.23.32 the test case I submitted apparently wo

Re: 3.23.31 gives FULLTEXT problems on sparc64 Linux

2001-01-19 Thread Sergei Golubchik
Hi! On Jan 19, Tibor Simko wrote: > Hello > > After upgrading to 3.23.31, FULLTEXT selects give often "error -1 from > table handler" for me. The error log says "ft_read_first: Got error > -1 when reading table foo". I think I have not seen those for older > 3.23.x versions (x=28 or so), at le

3.23.31 gives FULLTEXT problems on sparc64 Linux

2001-01-19 Thread Tibor Simko
Hello After upgrading to 3.23.31, FULLTEXT selects give often "error -1 from table handler" for me. The error log says "ft_read_first: Got error -1 when reading table foo". I think I have not seen those for older 3.23.x versions (x=28 or so), at least not that frequently. A small example to re