Re^7: Using the unicode61 tokenizer in DBD::SQLite

To expand a bit on the steps Anonymous Monk gave you, the steps would be:

Start the CPAN shell:
```
cpan
[download]
```
Download and unpack the DBD::SQLite distribution:
```
look DBD::SQLite
[download]
```

Recompile DBD::SQLite with the options that Anonymous Monk proposed:

perl Makefile.PL DEFINE=-DSQLITE_ENABLE_FTS4_UNICODE61
[download]

Watch the output for errors.
Run the tests
```
make test
[download]
```
Verify that Unicode now works in the way you expect it to.
Install the module if all tests pass and things work for you
```
make install
[download]
```

Comment on Re^7: Using the unicode61 tokenizer in DBD::SQLite Select or Download Code

Replies are listed 'Best First'.
Re^8: Using the unicode61 tokenizer in DBD::SQLite by elef (Friar) on Jan 08, 2014 at 10:05 UTC
Thanks, Corion. I saw that you are one of the maintainers. Any plans to enable the unicode61 tokenizer in future releases?	[reply]
Re^9: Using the unicode61 tokenizer in DBD::SQLite by Corion (Patriarch) on Jan 08, 2014 at 10:12 UTC
I only contributed some minor fixes to SQLite, but I'm not a real maintainer. I don't follow the development of DBD::SQLite closely, so I don't know the implications of always enabling the tokenizer. If there are no side effects other than compiled code for a feature that is likely to be unused, I don't think the real maintainers will object. I would write a mail to Kenichi Ishigaki with the proposed change and the idea why this change is harmless. Also, the changed Makefile.PL resp. the patch against the current Makefile.PL is more likely to get your changes into the next release.	[reply]