Re: [pysqlite] Compiled apsw on windows with no errors but it doesnt work

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart wrote:
> Thanks for the detailed reply.  I really dont want to have to compile 
> anything if I can help it and I would rather use the binary. Trouble is 
> I want to use fts3 - that is why I am trying apsw rather than sqlite3.

You were right that the Windows APSW distribution did not include FTS3
even though I claimed it did and showed that in the Makefile.  What had
happened was that the Makefile used --enable=fts instead of --enable=fts3.

I have done the following to fix this issue:

- - Corrected the Makefile

- - Added tests to the test suite that verify operation of the FTS3, RTree
and ICU extensions if they are present

- - Modified setup.py so that if the relevant --enable=extension option is
present and the test suite is invoked from setup.py then the test suite
will ensure the extension is present

- - Modified setup.py so that the --enable options are checked against a
known list so that typos like this will be caught.  (There are lots of
options so the test is weak - it allows through all with an underscore
or memsys in their name and only check the rest which are almost all
extension names.)  http://www.sqlite.org/compile.html#enablefeatures

The updated code and Windows binary distributions will be available in
the next release of APSW.  That release will be shortly after the next
SQLite release.  Those are approximately once a month.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkpcQR4ACgkQmOOfHg372QRn1gCgqaTuDnAfe9pJzp/sJgQd9WzT
Z4UAn3oucqlkYT4dzBFajS1eWSkmFzo+
=hqCR
-----END PGP SIGNATURE-----