[SVN-3387] SQLite configuration fails since client application has already configured SQLite

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.6.x
• Fix Version/s: 1.6.2
• Component/s: libsvn_subr
• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 30/Mar/09 04:13
• Updated: 27/Oct/18 16:34
• Resolved: 12/Apr/09 15:17

Description

The call to sqlite3_config fails in subversion due to the fact that the calling
application (Trac) has already initialized SQLite.

I am uncertain as to how this should be managed and thus cannot suggestion a
reasonable solution.  If possible, the current state for thread-safety of SQLite
should be queried before setting it.

In the mean-time, I am applying a temporary patch to ignore failure on setting
the state to multithreaded since my current application usage should hopefully
not call sqlite3_config(SQLITE_CONFIG_SINGLETHREAD).

Original issue reported by harningt