MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#756 — MySQL 5 - Support Strict-Mode
Attached to Project —
MODx
Opened by Ernst Joss (asihi) - Saturday, 13 January 2007, 01:46PM
Last edited by Jason Coward (opengeek) - Wednesday, 23 May 2007, 10:24PM
Opened by Ernst Joss (asihi) - Saturday, 13 January 2007, 01:46PM
Last edited by Jason Coward (opengeek) - Wednesday, 23 May 2007, 10:24PM
| Task Type | Feature Request |
|---|---|
| Category | Core Distribution |
| Status | Closed |
| Assigned To |
Jason Coward (opengeek) |
| Operating System | All |
| Severity | Low |
|---|---|
| Priority | Normal |
| Reported Version | 0.9.5 |
| Due in Version | 0.9.6 |
| Due Date | Undecided |
| Percent Complete |
|
Details
There are different locations where the strict-mode of MySQL 5 leads to sql-errors. Several where already reported and fixed up to now, some I have constated during my tests of modx. Try to add a new user and the sql-code for inserting the user attributes will break.Same behaviour as reported in bug id 167 and some forum posts. Solution is to disable strict mode on mysql-server. This seams to be no option for a production environment.
This task depends upon
This task blocks these from closing
Closed by Garry Nutting (garryn)
Friday, 19 September 2008, 07:51PM
Reason for closing: Fixed
Additional comments about closing: Considering this report fixed as of MODx 0.9.6.2. Please open a new ticket at http://svn.modxcms.com/jira if still experiencing issues. Thanks!
Friday, 19 September 2008, 07:51PM
Reason for closing: Fixed
Additional comments about closing: Considering this report fixed as of MODx 0.9.6.2. Please open a new ticket at http://svn.modxcms.com/jira if still experiencing issues. Thanks!
Basically, there are different parameters that can be set for STRICT mode which will affect the level of strictness that is applied - knowing which ones you are running under will help to diagnose the problems.
STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
I think the critical parameter here is the first one.
My SQL mode is also: STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
- Field changed: Status (Unconfirmed → Requires testing)
- Field changed: Due in Version (Undecided → 0.9.6)
- Field changed: Percent Complete (0% → 100%)
- Field changed: Due Date (Undecided → Undecided)
- Task assigned to Jason Coward (opengeek)
This is fixed as of revision 2756 in branches/0.9.6 and will be merged into trunk for 0.9.6 final release.