DBD::SQLite: renamed some of the "unicode" attribute in the pod to "sqlite_unicode" to resolve #50935 spotted by ASHLEY

Changes

@@ -1,5 +1,9 @@
 Changes for Perl extension DBD-SQLite
 
+1.26_07 to be released
+    - Resolved #50935: there remained old "unicode" attribute usage
+      in the pod, spotted by ASHLEY. (ISHIGAKI)
+
 1.26_06 Wed 28 Ocr 2009
     *** CHANGES THAT MAY POSSIBLY BREAK YOUR OLD APPLICATIONS ***
     - Removed undocumented (and most probably unused) reset method

lib/DBD/SQLite.pm

@@ -737,13 +737,20 @@ This is somewhat weird, but works anyway.
 Since SQLite 3.6.19 (released on Oct 14, 2009; bundled with
 DBD::SQLite 1.26_05), foreign key constraints are supported (though
 with some limitations). See L<http://www.sqlite.org/foreignkeys.html>
-for details. Though SQLite does NOT enable this feature by default yet (for backward compatibility), DBD::SQLite enables it internally. If you don't want this feature, issue a pragma to disable the feature.
+for details. Though SQLite does NOT enable this feature by default
+yet (for backward compatibility), DBD::SQLite enables it internally.
+If you don't want this feature, issue a pragma to disable the feature.
 
   $dbh->do("PRAGMA foreign_keys = OFF");
 
 =head2 Pragma
 
-SQLite has a set of "Pragma"s to modifiy its operation or to query for its internal data. These are specific to SQLite and are not likely to work with other DBD libraries, but you may find some of these are quite useful. DBD::SQLite actually sets some (like C<foreign_keys> above) for you when you connect to a database. See L<http://www.sqlite.org/pragma.html> for details.
+SQLite has a set of "Pragma"s to modifiy its operation or to query
+for its internal data. These are specific to SQLite and are not
+likely to work with other DBD libraries, but you may find some of
+these are quite useful. DBD::SQLite actually sets some (like
+C<foreign_keys> above) for you when you connect to a database.
+See L<http://www.sqlite.org/pragma.html> for details.
 
 =head2 Performance
 
@@ -818,7 +825,9 @@ updates:
 
 Defining the column type as C<BLOB> in the DDL is B<not> sufficient.
 
-As of version 1.26_06, C<unicode> is renamed to C<sqlite_unicode> for integrity. Old C<unicode> attribute is still accessible but will be deprecated in the near future.
+This attribute was originally named as C<unicode>, and renamed to
+C<sqlite_unicode> for integrity since version 1.26_06. Old C<unicode>
+attribute is still accessible but will be deprecated in the near future.
 
 =back
 
@@ -1367,10 +1376,10 @@ or
 
 =head2 Unicode handling
 
-If the attribute C<< $dbh->{unicode} >> is set, strings coming from
+If the attribute C<< $dbh->{sqlite_unicode} >> is set, strings coming from
 the database and passed to the collation function will be properly
 tagged with the utf8 flag; but this only works if the
-C<unicode> attribute is set B<before> the first call to
+C<sqlite_unicode> attribute is set B<before> the first call to
 a perl collation sequence . The recommended way to activate unicode
 is to set the parameter at connection time :
 
@@ -1378,7 +1387,7 @@ is to set the parameter at connection time :
       "dbi:SQLite:dbname=foo", "", "",
       {
           RaiseError     => 1,
-          unicode    => 1,
+          sqlite_unicode => 1,
       }
   );
 
@@ -1462,7 +1471,9 @@ Bugs should be reported via the CPAN bug tracker at
 
 L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=DBD-SQLite>
 
-Note that bugs of bundled sqlite library (i.e. bugs in C<sqlite3.[ch]>) should be reported to the sqlite developers at sqlite.org via their bug tracker or via their mailing list.
+Note that bugs of bundled sqlite library (i.e. bugs in C<sqlite3.[ch]>)
+should be reported to the sqlite developers at sqlite.org via their bug
+tracker or via their mailing list.
 
 =head1 AUTHORS