Software /
code /
prosody-modules
File
mod_log_messages_sql/README.markdown @ 4515:2e33eeafe962
mod_muc_markers: Prevent any markers from reaching the archive, even if untracked
Original intention was to leave alone things that this module isn't
handling. However markers in archives are just problematic without
more advanced logic about what is markable and what is not. It also
requires a more advanced query in mod_muc_rai to determine the latest
markable message instead of the latest archived message.
I'd rather keep the "is archivable" and "is markable" definition the
same for simplicity. I don't want to introduce yet another set of rules
for no reason.
No markers in MAM.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Mon, 22 Mar 2021 15:55:02 +0000 |
parent | 3438:b74c86d137c9 |
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`·