Mercurial > prosody-modules

view mod_log_messages_sql/README.markdown @ 5173:460f78654864

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_muc_rtbl: also filter messages This was a bit tricky because we don't want to run the JIDs through SHA256 on each message. Took a while to come up with this simple plan of just caching the SHA256 of the JIDs on the occupants. This will leave some dirt in the occupants after unloading the module, but that should be ok; once they cycle the room, the hashes will be gone. This is direly needed, otherwise, there is a tight race between the moderation activities and the actors joining the room.
author Jonas Schäfer <jonas@wielicki.name>
date Tue, 21 Feb 2023 21:37:27 +0100
parents b74c86d137c9
children
line wrap: on
line source

# Introduction

::: {.alert .alert-danger}
Consider using [mod_mam][doc:modules:mod_mam] together with
[mod_readonly] instead.
:::

This module logs messages to a SQL database.

SQL connection options are configured in a `message_log_sql` option,
which has the same syntax as the `sql` option for
[mod_storage_sql][doc:modules:mod_storage_sql].

# Usage

You will need to create the following table in the configured database:

``` sql
CREATE TABLE `prosodyarchive` (
        `host` TEXT,
        `user` TEXT,
        `store` TEXT,
        `id` INTEGER PRIMARY KEY AUTOINCREMENT,
        `when` INTEGER,
        `with` TEXT,
        `resource` TEXT,
        `stanza` TEXT);
```

# Compatibility

Does *NOT* work with 0.10 due to a conflict with the new archiving
support in `mod_storage_sql`ยท