[sqlite] Unable to compile fts2 as loadable extension
I was able to compile fts1 as a loadable extension but I am having a lot of issue with fts2. The first issue is a duplicate sqlite_api symbol found in fts2.c and fts2_tokenizer.c (due to the SQLITE_EXTENSION_INIT1 macro used in both files). I solved the issue using a: extern sqlite3_api_routines *sqlite3_api; in fts2_tokenizer.c. But now the linked reports missing sqlite3_malloc, sqlite3_free, sqlite3_realloc symbols. Do I have to link with sqlite3.c or I should just write some wrapper functions? Can fts2 be compiled as an external loadable extension? --- Marco Bambini http://www.sqlabs.net http://www.sqlabs.net/blog/ http://www.sqlabs.net/realsqlserver/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Unable to compile fts2 as loadable extension
Any reason why you don't want to use fts3 instead? Using fts2 means potential big consistency issues if you run vacuum on your database. Moreover, fts3 should just compile and run smoothly on latest versions. Alex. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Unable to compile fts2 as loadable extension
Yes I know and fts3 is enabled by default but I need to be able to load fts2 as an external extension for legacy support. --- Marco Bambini http://www.sqlabs.net http://www.sqlabs.net/blog/ http://www.sqlabs.net/realsqlserver/ On Oct 8, 2008, at 6:15 AM, Alexandre Courbot wrote: Any reason why you don't want to use fts3 instead? Using fts2 means potential big consistency issues if you run vacuum on your database. Moreover, fts3 should just compile and run smoothly on latest versions. Alex. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users