Nicolas Sebrecht 677afb8d8f sqlite: close the database when no more threads need access ... It's required to have more than one connection to the database for the maxconnections configuration option to work with threads. However, connection.close() is closing all the connections. Only close the connection when no more thread need it. Backported-from: 856b74407bd7f634cae5a8c2d9b84e13d14c12d2 Github-fix: https://github.com/OfflineIMAP/offlineimap/issues/350 Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>		2016-07-22 09:19:09 +02:00
..
__init__.py	Use "from . import" for relative imports	2012-02-06 17:41:43 +01:00
Base.py	Keywords: avoid warning at each message when no keywords are used	2015-11-22 20:05:34 +01:00
Gmail.py	fix: broken retry loop would break connection management	2015-11-26 17:11:59 +01:00
GmailMaildir.py	maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option	2015-04-07 11:54:35 +02:00
IMAP.py	fix: broken retry loop would break connection management	2015-11-26 17:11:59 +01:00
LocalStatus.py	sqlite: open database when we use it rather than at instantiation time	2016-06-08 01:59:39 +02:00
LocalStatusSQLite.py	sqlite: close the database when no more threads need access	2016-07-22 09:19:09 +02:00
Maildir.py	Identify and fix messages with FMD5 inconsistencies	2016-03-06 21:01:51 +01:00
UIDMaps.py	maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option	2015-04-07 11:54:35 +02:00