http://hg.omfa.de/prosody-hg/ en-us prosody-hg: util/sqlite3.lua history util/sqlite3.lua revision history util.sqlite3: Support immediate transactions http://hg.omfa.de/prosody-hg/log/52e214142ac2/util/sqlite3.lua Kim Alvefur <zash@zash.se> Mon, 19 Aug 2024 00:15:40 +0200 util.sql: Add API to start an explicit write transaction http://hg.omfa.de/prosody-hg/log/e7c52d0b0e0d/util/sqlite3.lua
This will be used in SQLite3 to BEGIN IMMEDIATE, which attempts to
acquire write locks immediately instead of when the first write
statement is started. Thus it would fail faster if the write lock is
already taken. Normally that should not occur but e.g. prosodyctl could
take it.

Investigating whether something similar is sensible in PostgreSQL, MySQL
is a future task.]]> Kim Alvefur <zash@zash.se> Mon, 19 Aug 2024 00:06:45 +0200 util.sql: SQLCipher support http://hg.omfa.de/prosody-hg/log/844e7bf7b48a/util/sqlite3.lua
This enables use of encrypted databases if LuaDBI or LuaSQLite3 has been
linked against SQLCipher. Using `LD_PRELOAD` may work as well.

Requires SQLCipher >= 4.0.0 due to the use of UPSERT]]> Kim Alvefur <zash@zash.se> Thu, 23 Jan 2025 16:38:56 +0100 util.sqlite3: Clean up unused variables http://hg.omfa.de/prosody-hg/log/f2578a69ccf4/util/sqlite3.lua
Many leftovers from the earlier version of util.sql this was based on
and cleanup applied there since then.]]> Kim Alvefur <zash@zash.se> Sat, 22 Jul 2023 14:54:17 +0200 util.sqlite3: Don't cache prepared statements for one-off queries http://hg.omfa.de/prosody-hg/log/e560f7c691ce/util/sqlite3.lua
The :execute method is mainly used for one-off queries such as creating
tables and indices. There is no need to cache this prepared statement,
as those queries are only done on startup.

Further, prepared statements can't be reused without being reset, so
this was likely broken anyway.]]> Kim Alvefur <zash@zash.se> Sat, 10 Jun 2023 22:20:26 +0200 util.sqlite3: Deduplicate query methods http://hg.omfa.de/prosody-hg/log/771eb453e03a/util/sqlite3.lua
There were 3 very similar methods:
- :execute()
- :execute_query()
- :execute_update()

The first one returns the prepared statement and is mainly used
internally in the library for CREATE statements.

The later two only really differ in how the results are returned.
Those two are one main method and one small one that only picks out the
iterator.]]> Kim Alvefur <zash@zash.se> Sat, 10 Jun 2023 22:02:15 +0200 util.sqlite3: Fix indentation http://hg.omfa.de/prosody-hg/log/af251471d5ae/util/sqlite3.lua Kim Alvefur <zash@zash.se> Sat, 10 Jun 2023 22:00:43 +0200 util: Prefix module imports with prosody namespace http://hg.omfa.de/prosody-hg/log/d10957394a3c/util/sqlite3.lua Kim Alvefur <zash@zash.se> Fri, 17 Mar 2023 16:23:16 +0100 mod_storage_sql: Record connection to database as module status http://hg.omfa.de/prosody-hg/log/a20923f7d5fd/util/sqlite3.lua
Allows retrieving this in e.g. a health reporting module

Thanks pfak]]> Kim Alvefur <zash@zash.se> Mon, 30 Jan 2023 00:38:26 +0100 util.sqlite3: Skip prepared statements when no parameters are given http://hg.omfa.de/prosody-hg/log/ccb030d988ac/util/sqlite3.lua
Seems CREATE INDEX is unhappy as a prepared statement. Perhaps because
the table has not been COMMIT-ed yet?]]> Kim Alvefur <zash@zash.se> Mon, 01 Aug 2022 17:25:40 +0200 util.sqlite3: Create util.error registry from headers http://hg.omfa.de/prosody-hg/log/d6cdde74cd9b/util/sqlite3.lua
The 'type' fields are a first guess.]]> Kim Alvefur <zash@zash.se> Fri, 01 Oct 2021 02:27:53 +0200 util.sqlite3: SQLite3-only variant of util.sql using LuaSQLite3 http://hg.omfa.de/prosody-hg/log/f306336b7e99/util/sqlite3.lua
http://lua.sqlite.org/]]> Kim Alvefur <zash@zash.se> Mon, 01 Aug 2022 15:23:33 +0200