On Monday, December 21, 2009 at 9:52:17 PM UTC+11, Thomas Mueller Graf
wrote:
>
> Hi,
>
> Thanks for your help! I can now reproduce the problem. The problem is
> that currently, before inserting or deleting data, FT_INIT() has to be
> called (only for the native fulltext search; not for the Lucene
> search).
>
> That's a bug of course, I will fix it for the next release.
>
Hi Thomas, I see this seems to be a problem with 1.4.192. I don't know the
exact steps to reproduce, however; what I am doing is dropping all objects
then loading using runscript.
I rebuild using the following:
drop all objects;
runscript from '/Users/bryan/Development/db/backup/local_mmm.sql.gz'
compression gzip;
CREATE ALIAS IF NOT EXISTS FT_INIT FOR "org.h2.fulltext.FullText.init";
CALL FT_INIT();
CALL FT_DROP_INDEX('PUBLIC', 'CARDSADDRESS');
CALL FT_CREATE_INDEX('PUBLIC', 'CARDSADDRESS', null);
At the point before FT_INIT() no schema for FT exists. After FT_INIT FT
schema and tables exist with no content. FT_DROP_INDEX was used just to see
if it would help, it didn't.
Once I run FT_CREATE_INDEX I get:
Error code 23505, SQL state 23505: Unique index or primary key violation:
"PRIMARY_KEY_1 ON FT.MAP(WORDID, ROWID) VALUES (1, 57336, 727241)"; SQL
statement:
INSERT INTO FT.MAP(ROWID, WORDID) VALUES(?, ?) [23505-192]
No trace information is present from the DB.
Note, I have successfully created this index in the past.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
