simcop2387/DBD-SQLite-SQLcipher
1
0
Fork 0
mirror of https://github.com/DBD-SQLite/DBD-SQLite synced 2025-06-07 14:19:10 -04:00
Code Issues Releases Wiki Activity

Merge pull request #89 from FGasper/fix_sqlite_unicode_pod

Browse source 
Remove mention of now-deprecated “sqlite_unicode” parameter.
This commit is contained in:
Kenichi Ishigaki 2021-08-03 10:40:08 +09:00 • committed by GitHub
commit 711f90b8c7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
lib/DBD/SQLite.pm
View file

@ -2589,18 +2589,17 @@ or
=head2 Unicode handling =head2 Unicode handling
If the attribute C<< $dbh->{sqlite_unicode} >> is set, strings coming from Depending on the C<< $dbh->{sqlite_string_mode} >> value, strings coming
the database and passed to the collation function will be properly from the database and passed to the collation function may be decoded as
tagged with the utf8 flag; but this only works if the UTF-8. This only works, though, if the C<sqlite_string_mode> attribute is
C<sqlite_unicode> attribute is set B<before> the first call to set B<before> the first call to a perl collation sequence. The recommended
a perl collation sequence . The recommended way to activate unicode way to activate unicode is to set C<sqlite_string_mode> at connection time:
is to set the parameter at connection time :
my $dbh = DBI->connect( my $dbh = DBI->connect(
"dbi:SQLite:dbname=foo", "", "", "dbi:SQLite:dbname=foo", "", "",
{ {
RaiseError => 1, RaiseError => 1,
sqlite_unicode => 1, sqlite_string_mode => DBD_SQLITE_STRING_MODE_UNICODE_STRICT,
} }
); );