From fc491a64a9eadb799cbdbbe403ce99e0e6779fc1 Mon Sep 17 00:00:00 2001
From: Kenichi Ishigaki <ishigaki@cpan.org>
Date: Sun, 23 Dec 2018 02:13:04 +0900
Subject: [PATCH] add more examples for sqlite_db_config (wyant++)

---
 lib/DBD/SQLite.pm | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/lib/DBD/SQLite.pm b/lib/DBD/SQLite.pm
index 74bade6..e4f7544 100644
--- a/lib/DBD/SQLite.pm
+++ b/lib/DBD/SQLite.pm
@@ -2321,6 +2321,13 @@ You can change how the connected database should behave like this:
   # This disables language features that allow ordinary SQL
   # to deliberately corrupt the database file
   $dbh->sqlite_db_config( SQLITE_DBCONFIG_DEFENSIVE, 1 );
+  
+  # This disables two-arg version of fts3_tokenizer.
+  $dbh->sqlite_db_config( SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER, 0 );
+
+C<sqlite_db_config> returns the new value after the call. If you just want to know the current value without changing anything, pass a negative integer value.
+
+  my $current_value = $dbh->sqlite_db_config( SQLITE_DBCONFIG_DEFENSIVE, -1 );
 
 As of this writing, C<sqlite_db_config> only supports options that set an integer value. C<SQLITE_DBCONFIG_LOOKASIDE> and C<SQLITE_DBCONFIG_MAINDBNAME> are not supported. See also C<https://www.sqlite.org/capi3ref.html#sqlite3_db_config> for details.