| Summary | Problem with MySQL and many filter rules |
| Queue | Ingo |
| Queue Version | 1.1.3 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | burghardt (at) riege (dot) com |
| Created | 08/20/2007 (6501 days ago) |
| Due | |
| Updated | 08/22/2007 (6499 days ago) |
| Assigned | |
| Resolved | 08/22/2007 (6499 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
in Horde 3.2, any change to a preference that would overflow the
maxsize configuration parameter is rejected to preserve the existing
data.
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Problem with MySQL and many filter rules
Queue ⇒ Ingo
using the current stable release of Horde and Ingo in conjunction with
Cyrus IMAPD 2.2.12 (+Sieve) and MySQL 4.1.20, we discovered the
following problem:
* a user had a lot of rules
* he added one rule and the rule overview on the web page became empty
On database level happened:
* the 'pref_value' field (type: text) in the 'horde_prefs' table was
filled with 65535 characters as all rules are written with a special
syntax to this field.
* The final rule was cut off in the middle of the description entry
because it did not fit completely into to database field anymore
* As the syntax was broken the web page became empty.
Probably, it will be better to save the filter rules into an own
database table with each rule as one data entry.
Best regards,
Heiko