| Summary | Mysqli improvements for catching errors/warnings |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | slusarz (at) horde (dot) org |
| Created | 02/19/2013 (4518 days ago) |
| Due | |
| Updated | 03/01/2013 (4508 days ago) |
| Assigned | |
| Resolved | 03/01/2013 (4508 days ago) |
| Milestone | |
| Patch | No |
partitioning and strict modes in MySQL manual).
2. I don't think it is a good idea to enable strict mode in general
Horde code. It's a performance penalty and it fixes nothing for us who
store sessions on filesystem or elsewhere than database.
Yes, what Horde could do is to check a warning count and log them. But
I don't see how this is useful for anything more than debuging
purposes. As for the strict mode enablement, if system administrator
wants, he could enable it in MySQL configuration.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Assigned to
Queue ⇒ Horde Framework Packages
Summary ⇒ Mysqli improvements for catching errors/warnings
Type ⇒ Enhancement
State ⇒ Assigned
Patch is attached to message.