Mercurial > prosody-modules

view mod_log_messages_sql/README.markdown @ 5285:8e1f1eb00b58

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.
author Matthew Wild <mwild1@gmail.com>
date Wed, 29 Mar 2023 16:12:15 +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`ยท