Has anybody had a chance to look at this ? I deleted all the FT.WORDS entries. This solved the problem only for a couple of hours. The problem is back by now. In the meantime, I recreated my database without the fulltext indexing, which was the main reason I went to H2 in place of HSQLDB.
If nobody knows the solution to this, then is there an SQL statement to remove and recreate a Fulltext Index, or to rebuild it ? So that if I get the error again, I could in my application rebuild the index, with the hopes that I solves the problem. Regards, Laurent On Dec 3, 12:17 am, lvr123 <[email protected]> wrote: > On Dec 2, 8:05 pm, Kerry Sainsbury <[email protected]> wrote:> Could it be > that you have a unique index on the column, and you've attempted > > to insert the same value twice...? > > Actually, I read something like this in an early topic, and it was not > possible to build a test case. And this is also the second time it > arises. > Because the problem is not in one of my indexes but in one of the > fulltext FT. schema indexes, in which tables and indexes are managed > by the H2 engine. > > My opinion is that this is a bug in H2. > > I managed to "solve" the problem by deleting all records in the table > FT.WORDS. This is not a sound manipulation. Before I deleted all, I > had 4 entries in that table with ids 1,2,3,5. I don't how the fulltext > engine works. Is that normal that I had that gap in the ids of the > FT.WORDS table ? > > Laurent > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
