From 0c6d966f1c438558c682c5c58b96b883f68d47d1 Mon Sep 17 00:00:00 2001
From: Bjoern Hoehrmann <bjoern@hoehrmann.de>
Date: Sat, 17 Apr 2021 14:13:48 +0200
Subject: [PATCH] Note conflict between SQLITE_THREADSAFE default and
 extensions that need sqlite3_mutex_* functions

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

diff --git a/lib/DBD/SQLite.pm b/lib/DBD/SQLite.pm
index 7f35bc7..ab4aca8 100644
--- a/lib/DBD/SQLite.pm
+++ b/lib/DBD/SQLite.pm
@@ -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