|Think about Loose Coupling|
Re: Using the unicode61 tokenizer in DBD::SQLiteby Anonymous Monk
|on Jan 06, 2014 at 02:28 UTC||Need Help??|
I just updated DBD::SQLite to 1.40 and made sure I have SQLite version 3.7.17.
But what does DBD::SQLite have, what is sqlite_version? update: I see you got it #define SQLITE_VERSION "3.7.17"
Was SQLite compiled without enabling the unicode61 tokenizer? (Some sources mention compiling sqlite with SQLITE_ENABLE_FTS4_UNICODE61 in order to get this functionality.)
I see that that conditional is in the source /* fts3_unicode2.c (functions generated by parsing unicode text files) */ #ifdef SQLITE_ENABLE_FTS4_UNICODE61 but since you get an error message, it probably wasn't compiled with that turned one ( nothing turned on in source)
Do I have any options here?
I think recompile with perl Makefile.PL DEFINE=-DSQLITE_ENABLE_FTS4_UNICODE61 and give it a shot
update: I just recompiled, all tests passed except some in t/51_table_column_metadata.t , same with cpanp -z ISHIGAKI/DBD-SQLite-1.41_03.tar.gz
same with perl Makefile.PL "DEFINE=-DSQLITE_ENABLE_FTS4_UNICODE61 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS3_PARENTHESIS "
Seems to work