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
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
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
