I seem to have missed that bit. Are you saying that the unicode61 tokenizer works out of the box in 1.41_03?

I don't know; If the stuff I copy/pasted means unicode61 is working, then I guess it is.

I got 1.41_03 installed using the cpan shell with install ISHIGAKI/DBD-SQLite-1.41_03.tar.gz.
Still no dice:

use strict;
use warnings;

use DBI;

my $dbh = DBI->connect( "dbi:SQLite:dbname=test.db",
                            "",
                            "", {
                                # RaiseError => 1,        # we'll hand
+le the errors ourselves
                                sqlite_unicode => 1,
                            }
                        ) or die "Can't connect to database: $DBI::err
+str";



my $sqliteversion = $dbh->{sqlite_version}; print "\nSQLite version: $
+sqliteversion\n";

$dbh->do("DROP TABLE IF EXISTS data") or print "drop table failed";



$dbh->do("CREATE VIRTUAL TABLE data USING fts4 (col1 TEXT, col2 TEXT, 
+tokenize=unicode61)") or print "failed to create fts4 table";
[download]


Output:


SQLite version: 3.8.0.2
DBD::SQLite::db do failed: unknown tokenizer: unicode61 at e:\uni612.p
+l line 22.

failed to create fts4 table
[download]

Yes, according to DBD::SQLite it should work out of the box.

See Re: Using the unicode61 tokenizer in DBD::SQLite, it it requires custom -DEFINES it doesn't work out of the box, it requires custom -DEFINES