Feeling Lucky
?
?
[#11526] - mySQL 5.7 nullDate compatibility fix
- Closed
- 9 Aug 2016
- Medium
- Build: staging
- # 11526
- Diff
- wmchris:staging
- Failure continuous-integration/travis-ci/pr The Travis CI build failed Details
User tests: Successful: Unsuccessful:
Summary of Changes
implemented the nullDate change for mysql 5.7 (from 0000-00-00 00:00:00 to 1000-01-01 00:00:00)
Testing Instructions
installation and/or updating on mysql 5.6 server, all datetime database default values of joomla should be 0000-00-00 00:00:00,
on installation and/or updating on mysql 5.7 server, all datetime database default values of joomla should be 1000-01-01 00:00:00
this could break external components, who rely on hardcoded nullDates.
joomla-cms-bot
- | Category | ⇒ | Administration Components SQL Installation Libraries |
| Status | New | ⇒ | Pending |
| Labels |
Added:
?
|
||
| Category | Administration Components SQL Installation Libraries | ⇒ | Repository Administration Components SQL Language & Strings Templates (admin) Front End Installation |
| Labels |
Added:
?
|
||
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-08-09 12:09:16 |
| Closed_By | ⇒ | wmchris |
this patch has been created at @icampus
it also implements #11527
the update routine should work in both ways (upgrade and downgrade of mysql version) - downgrade is experimental.