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

Merge pull request #72 from pullhub/sqlite_load_extension-vs-threadsafe

Browse source 
Note conflict between SQLITE_THREADSAFE default and extensions in POD
This commit is contained in:
Kenichi Ishigaki 2021-04-17 22:48:33 +09:00 • committed by GitHub
commit f066bb49ad
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
lib/DBD/SQLite.pm
View file

@ -2264,6 +2264,10 @@ SQLite3 extensions. After the call, you can load extensions like this:
Loading an extension by a select statement (with the "load_extension" SQLite3 function like above) has some limitations. If you need to, say, create other functions from an extension, use this method. $file (a path to the extension) is mandatory, and $proc (an entry point name) is optional. You need to call C<sqlite_enable_load_extension> before calling C<sqlite_load_extension>.
If the extension uses SQLite mutex functions like C<sqlite3_mutex_enter>, then
the extension should be compiled with the same C<SQLITE_THREADSAFE> compile-time
setting as this module, see C<DBD::SQLite::compile_options()>.
=head2 $dbh->sqlite_trace( $code_ref )
This method registers a trace callback to be invoked whenever