Mercurial > prosody-modules
view mod_log_messages_sql/README.markdown @ 4651:8231774f5bfd
mod_cloud_notify_encrypted: Ensure body substring remains valid UTF-8
The `body:sub()` call risks splitting the string in the middle of a
multi-byte UTF-8 sequence. This should have been caught by util.stanza
validation, but that would have caused some havoc, at the very least causing
the notification to not be sent.
There have been no reports of this happening. Likely because this module
isn't widely deployed among users with languages that use many longer UTF-8
sequences.
The util.encodings.utf8.valid() function is O(n) where only the last
sequence really needs to be checked, but it's in C and expected to be fast.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 22 Aug 2021 13:22:59 +0200 |
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`ยท