summaryrefslogtreecommitdiff
path: root/searx/data
diff options
context:
space:
mode:
authorMarkus Heiser <markus.heiser@darmarit.de>2025-09-27 15:35:43 +0200
committerMarkus Heiser <markus.heiser@darmarIT.de>2025-09-28 07:32:41 +0200
commit2f0d96b8bca36c35f3945badae69a4353fcff93c (patch)
tree2356b8c6c7c0c66f68b9a8237fd7d2db7e3ee0ac /searx/data
parent18a58943ccaa324b39232fa503462eb39f407399 (diff)
[fix] sqlitedb: DB connector -- unset isolation_level
A Connection object can be used as a context manager that automatically commits or rolls back open transactions when leaving the body of the context manager. If the connection attribute ``isolation_level`` is **not** ``None``, new transactions are implicitly opened before ``execute()`` and ``executemany()`` executes SQL- INSERT, UPDATE, DELETE, or REPLACE statements [1]. The old implementation set ``isolation_level`` to ``None`` and thereby prevented the context manager from opening and closing the transaction scopes. [1] https://docs.python.org/3/library/sqlite3.html#sqlite3-transaction-control-isolation-level [2] https://github.com/searxng/searxng/pull/5239#discussion_r2381416731 Reported-by: Ivan G <igabaldon@inetol.net> [2] Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'searx/data')
0 files changed, 0 insertions, 0 deletions