Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Merge 0.12->trunk | Kim Alvefur | 2023-01-06 | 1 | -14/+12 |
|\ | |||||
| * | mod_storage_sql: Fix #1639 | Kim Alvefur | 2023-01-01 | 1 | -14/+12 |
| | | | | | | | | Patch by Peter Kieser | ||||
* | | Merge 0.12->trunk | Kim Alvefur | 2022-12-29 | 1 | -1/+0 |
|\| | |||||
| * | mod_storage_sql: Don't avoid initialization under prosodyctl (fix #1787) | Kim Alvefur | 2022-12-29 | 1 | -1/+0 |
| | | | | | | | | | | | | | | | | | | Fixes `prosodyctl adduser` etc. Prior to d580e6a57cbb the line did nothing. Sometimes storage in the prosodyctl context does cause weirdness, as it is not in a host context, but rather a variant of global. | ||||
* | | mod_storage_sql: Strip timestamp precision in queries to fix error (thanks ↵ | Kim Alvefur | 2022-09-07 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | muppeth) Fixes Error in SQL transaction: Error executing statement parameters: ERROR: invalid input syntax for integer This was handled for INSERT in 9524bb7f3944 but not SELECT. | ||||
* | | mod_storage_sql: Drop archive timestamp precision pending schema update | Kim Alvefur | 2022-08-14 | 1 | -1/+2 |
| | | | | | | | | | | | | The "when" column is an INTEGER which will probably be unhappy about storing higher precision timestamps, so we keep the older behavior for now. | ||||
* | | Merge 0.12->trunk | Kim Alvefur | 2022-07-29 | 1 | -4/+2 |
|\| | |||||
| * | mod_storage_sql: Fix summary API with Postgres (fixes #1766) | Kim Alvefur | 2022-07-22 | 1 | -4/+2 |
| | | | | | | | | | | | | | | The ORDER BY and LIMIT clauses are not needed and don't even make much sense. This part was most likely a leftover from the :find method. Tested with sqlite and postgres 14 | ||||
* | | Merge 0.12->trunk | Kim Alvefur | 2022-07-27 | 1 | -1/+1 |
|\| | |||||
| * | mod_storage_sql: Fix bypass of load procedure under prosodyctl | Kim Alvefur | 2022-07-26 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | There's no 'prosody.prosodyctl' property other than this one, introduced in 6216743c188c in 2015. Guessing that the intent was to skip this when running as a prosodyctl command. The module.command code does its own version of this initialization, so this seems likely. Thanks raja for noticing | ||||
* | | compat: Remove handling of Lua 5.1 location of 'unpack' function | Kim Alvefur | 2022-07-11 | 1 | -1/+1 |
| | | |||||
* | | mod_storage_sql: Remove Lua 5.1 compatibility hack | Kim Alvefur | 2022-07-02 | 1 | -2/+1 |
|/ | | | | Part of #1600 | ||||
* | mod_storage_sql: Return cached total where it makes sense | Kim Alvefur | 2021-11-30 | 1 | -4/+9 |
| | | | | | This should skip the summary SQL query when not needed, ie when the cached value can be used directly. | ||||
* | mod_storage_sql: Adjust handling of 'total' for multi-id queries | Kim Alvefur | 2021-11-30 | 1 | -2/+3 |
| | | | | | Otherwise a query for a set of ids may cause that value to be cached, despite only covering a subset. | ||||
* | mod_storage_sql: Fix traceback on multi-user deletion | Kim Alvefur | 2021-11-30 | 1 | -2/+6 |
| | | | | | | | jid.join(true, ...) fails. Since we don't know which users this affects, best to clear the whole cache. | ||||
* | mod_storage_sql: Expose multi-user deletion capability | Kim Alvefur | 2021-11-30 | 1 | -0/+1 |
| | | | | | archive_store:delete(true) deletes messages for all users, which would allow some simplification when this is supported. | ||||
* | mod_storage_sql: Fix for move of yes/no function (Thanks Kasim) | Kim Alvefur | 2021-06-21 | 1 | -2/+2 |
| | |||||
* | mod_storage_sql: Implement map-like API for archives | Kim Alvefur | 2021-02-01 | 1 | -0/+47 |
| | | | | | | | | Used by mod_http_file_share, muc moderation, etc. Tests tweaked because they failed on stanza internals that happen becasue of re-serialization. Namespaces differ since inheritance is implicit when building but explicit after parsing. | ||||
* | mod_storage_sql: Fix compatibilty with Lua 5.1 | Kim Alvefur | 2021-01-13 | 1 | -1/+2 |
| | | | | | | string.rep() doesn't have the 3rd argument before Lua 5.2 Revert once we drop support for Lua 5.1 | ||||
* | mod_storage_sql: Support query for set of IDs | Kim Alvefur | 2021-01-12 | 1 | -0/+10 |
| | | | | Not compatible with Lua 5.1 | ||||
* | mod_storage_sql: Advertise support for id range query | Kim Alvefur | 2021-01-09 | 1 | -0/+1 |
| | | | | That is, a query for items between two IDs (not inclusive). | ||||
* | mod_storage_sql: Measure hits/misses on the item count cache | Kim Alvefur | 2020-07-02 | 1 | -0/+7 |
| | | | | | A cache miss can be expensive so having numbers on how often this occurs may be valuable. | ||||
* | mod_storage_sql: Fix incorrect results when fetching items before specific ↵ | Matthew Wild | 2020-06-12 | 1 | -1/+1 |
| | | | | | | archive id Copy/paste error, introduced in deb68066c7aa | ||||
* | mod_storage_sql: Log database connection parameters when creating engine | Kim Alvefur | 2020-05-02 | 1 | -2/+3 |
| | | | | | | This is meant to help trace down an issue where Prosody apparently creates multiple conflicting SQL engines, causing problems especially with SQLite3, e.g. #616 #784. | ||||
* | Merge 0.11->trunk | Kim Alvefur | 2020-03-22 | 1 | -0/+1 |
|\ | |||||
| * | mod_storage_sql: Add index covering sort_id to improve performance (fixes #1505) | Kim Alvefur | 2020-03-22 | 1 | -0/+1 |
| | | |||||
* | | storagemanager, mod_storage_sql: Rename methods to :get_all() and :delete_all() | Matthew Wild | 2020-03-11 | 1 | -4/+4 |
| | | |||||
* | | mod_storage_sql: Add map_store:find_key() and map_store:delete_key() (+ tests) | Matthew Wild | 2020-03-11 | 1 | -0/+44 |
| | | |||||
* | | Merge 0.11->trunk | Kim Alvefur | 2020-02-22 | 1 | -6/+6 |
|\| | |||||
| * | mod_storage_sql: Move update limit check back one step, fixes traceback | Kim Alvefur | 2020-02-22 | 1 | -6/+6 |
| | | | | | | | | | | 0c00274528a4 moved it one step too far, so the check was performed before connecting to the database instead of after. | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2020-02-21 | 1 | -7/+7 |
|\| | |||||
| * | mod_storage_sql: Fix check for deletion limits (fixes #1494) | Kim Alvefur | 2020-02-21 | 1 | -7/+7 |
| | | | | | | | | | | The check was only performed if sql_manage_tables was set to true (the default) It should always be performed | ||||
* | | mod_storage_sql: Remove unused and not actually returned return value [luacheck] | Kim Alvefur | 2019-12-24 | 1 | -1/+1 |
| | | | | | | | | The :delete throws an error, it does not return one like this. | ||||
* | | mod_storage_*: Also include timestmap of first message in :summary API | Kim Alvefur | 2019-08-23 | 1 | -3/+5 |
| | | | | | | | | | | For completeness along with most recent timestamp. Might be nice to be able to order by oldest unread message. | ||||
* | | mod_storage_*: Include timestamp of latest message in :summary API | Kim Alvefur | 2019-08-23 | 1 | -1/+4 |
| | | | | | | | | | | | | | | Clients may want to show a list of conversations ordered by how timestamp of most recent message. The counts allow a badge with unread message counter. | ||||
* | | mod_storage_*: Tweak :summary API to allow future expansion with more fields | Kim Alvefur | 2019-08-23 | 1 | -3/+5 |
| | | | | | | | | Eg might want to include last message, timestamp, chat state or other info. | ||||
* | | mod_storage_sql: Ignore shadowed error variable [luacheck] | Kim Alvefur | 2019-05-28 | 1 | -1/+1 |
| | | |||||
* | | mod_storage_sql: Fix to use correct arguments to archive id lookup | Kim Alvefur | 2019-05-28 | 1 | -2/+2 |
| | | |||||
* | | mod_storage_sql: Correctly return item-not-found error | Kim Alvefur | 2019-05-28 | 1 | -2/+3 |
| | | | | | | | | `return ok, err` comes out as `transaction_ok, ok, err` | ||||
* | | mod_storage_sql: Look up archive IDs in separate queries (fixes #1325) | Kim Alvefur | 2019-03-23 | 1 | -29/+29 |
| | | | | | | | | This is probably not good for performance. | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2019-05-26 | 1 | -14/+22 |
|\| | |||||
| * | mod_storage_sql: Handle SQLite DELETE with LIMIT being optional (fixes #1359) | Kim Alvefur | 2019-05-13 | 1 | -6/+15 |
| | | |||||
| * | mod_storage_sql: Move code out of if-else chain | Kim Alvefur | 2019-05-13 | 1 | -9/+8 |
| | | |||||
* | | mod_storage_sql: Add support for iterating over users in archive stores | Kim Alvefur | 2019-05-05 | 1 | -0/+13 |
| | | |||||
* | | mod_storage_sql: Implement archive summary API | Kim Alvefur | 2019-02-25 | 1 | -0/+35 |
| | | |||||
* | | mod_storage_sql: No archive item limit by default | Kim Alvefur | 2019-03-22 | 1 | -4/+6 |
| | | |||||
* | | mod_storage_sql: Return cached count if only this is queried for | Kim Alvefur | 2019-03-22 | 1 | -1/+5 |
| | | |||||
* | | mod_storage_sql: Cache total count if it's calculated as part of the current ↵ | Kim Alvefur | 2019-03-22 | 1 | -0/+3 |
| | | | | | | | | query | ||||
* | | mod_storage_sql: Skip cache write | Kim Alvefur | 2019-03-22 | 1 | -1/+0 |
| | | | | | | | | | | This would cause the cache to be wrong in case the the later INSERT fails and the transaction is aborted. | ||||
* | | mod_storage_sql: Fix to use currently queried store | Kim Alvefur | 2019-03-22 | 1 | -2/+2 |
| | | | | | | | | | | Was using the previously queried store due to this being cached in an upvalue. |