Mercurial > prosody-modules
view mod_log_messages_sql/README.markdown @ 5820:742142f9771e
mod_groups_internal: Fix traceback when room doesn't exist
I'm not sure if it should even be included if it doesn't exist, but I'm not
currently sure how this situation occurs, so I'm implementing the lightest
possible fix for now.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 11 Jan 2024 15:53: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`ยท