Enable Full-Text Search by Default

[iansinnott]

This is just a suggestion, since there are tradeoffs.

The good:

• Parity with sqlite3. Since FTS 3, 4, 5 are enabled in the default build of sqlite most users are likely familiar with.
• Users don't need to figure out how to modify the Makefile in order to use FTS features (i.e. via questions like Full text support #77)

The bad:

• Increased bundle size. On my own system the async wasm bundle went from 1.3mb to 1.5mb.

What would need to be done:

In the Makefile, add new WASQLITE_DEFINES:

	-DSQLITE_ENABLE_FTS5 \
	-DSQLITE_ENABLE_FTS4 \ # optional
	-DSQLITE_ENABLE_FTS3 \ # optional

[rhashimoto]

Another argument for:

• The official SQLite WASM build includes FTS5, by my reading of the makefile.

And against:

• The current build settings are based on the recommended options, which don't include FTS.

Unfortunately, I don't have any real data on how developers use (or want to use) wa-sqlite, so it's hard to evaluate that trade off and I should probably default to not making things bigger and slower for the existing user base. Perhaps the way to go with this would be to include two .wasm builds (each with and without Asyncify), one with the current settings and an additional "kitchen sink" variation that favors features over size and more thorough testing.

[sgbeal]

The official SQLite WASM build includes FTS5, by my reading of the makefile.

Just to confirm: that is indeed the case. For the wasm build, since it's a new target platform for us, we've opted against including deprecated features by default (which includes, for example, the "double-quoted-string" support).

[rhashimoto]

I added a dist-xl build target with additional features enabled, including FTS5. This target is not built (or tested) by default - instead I'll attach the artifacts produced to the release message.