https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8463
Bug ID: 8463
Summary: SQL user preferences can be overridden by @GLOBAL
ones, depending on the database collation
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Libraries
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: Undefined
Created attachment 6155
--> https://bz.apache.org/SpamAssassin/attachment.cgi?id=6155&action=edit
order SQL user preference rows with CASE instead of by username
SQL user preferences rely on ORDER BY username to read the @GLOBAL rows before
the user's own, so that the user's settings override global and domain
settings. The default query and the examples in the documentation of
user_scores_sql_custom_query can sort in a different order, varying with MySQL,
MariaDB, and PostgreSQL, in combination with collation settings. With some,
global settings override the user's.
The attached patch orders the rows explicitly in the default query and in the
examples, in a way that does not depend on the collation and works in MySQL,
MariaDB and PostgreSQL. It applies on top of the patch in bug 8462.
--
You are receiving this mail because:
You are the assignee for the bug.
