Mercurial > prosody-modules
view mod_log_messages_sql/README.markdown @ 4876:0f5f2d4475b9
mod_http_xep227: Add support for import via APIs rather than direct store manipulation
In particular this transitions PEP nodes and data to be imported via mod_pep's
APIs, fixing issues with importing at runtime while PEP data may already be
live in RAM.
Next obvious candidate for this approach is rosters, so clients get immediate
roster pushes and other special handling (such as emitting subscribes to reach
the desired subscription state).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Tue, 18 Jan 2022 17:01:18 +0000 |
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`ยท