Upgrade: confirm MySql v5.6 compatibility
Reported by dleffler | February 11th, 2013 @ 04:37 PM | in 2.2.0release-candidate (closed)
We seem to be incompatible with the latest version(s) of MySql, (at least v5.6.10 on Win32) primarily because empty and/or null are NOT acceptible in an integer field.
Comments and changes to this ticket
-
dleffler February 16th, 2013 @ 02:56 AM
- Milestone changed from “2.2.0alpha2” to “2.2.0alpha3”
-
dleffler March 2nd, 2013 @ 09:43 PM
- Milestone changed from “2.2.0alpha3” to “2.2.0beta1”
-
-
dleffler March 16th, 2013 @ 03:28 AM
- Milestone changed from “2.2.0beta1” to “2.2.0beta2”
-
dleffler March 29th, 2013 @ 08:00 PM
- Milestone changed from “2.2.0beta2” to “2.2.0beta3”
-
dleffler April 20th, 2013 @ 10:17 AM
- Milestone changed from “2.2.0beta3” to “2.2.0release-candidate”
-
dleffler April 25th, 2013 @ 12:16 PM
This error doesn't seem to occur w/ MySQL v5.6.11 (win 32) like it did under v5.6.10
-
dleffler April 27th, 2013 @ 11:47 PM
- Title changed from “Bug: Incompatible/Errors w/ MySql v5.6” to “Upgrade: confirm MySql v5.6 compatibility”
-
dleffler April 29th, 2013 @ 11:21 AM
- Assigned user set to “expNinja”
- Milestone changed from “2.2.0release-candidate” to “2.2.1”
-
dleffler April 29th, 2013 @ 11:23 AM
- State changed from “new” to “resolved”
- Assigned user changed from “expNinja” to “dleffler”
- Milestone changed from “2.2.1” to “2.2.0release-candidate”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
dleffler
expNinja