[wp-trac] [WordPress Trac] #8857: Make WP MySQL strict mode compliant
WordPress Trac
noreply at wordpress.org
Mon Jan 22 08:45:44 UTC 2024
#8857: Make WP MySQL strict mode compliant
-------------------------+-----------------------
Reporter: ghostks | Owner: (none)
Type: enhancement | Status: reopened
Priority: lowest | Milestone:
Component: Database | Version: 6.4.2
Severity: normal | Resolution:
Keywords: | Focuses:
-------------------------+-----------------------
Changes (by pounibi):
* status: closed => reopened
* version: 2.7 => 6.4.2
* resolution: wontfix =>
* severity: minor => normal
Comment:
THX for setting minimal MySQL version to 5.5.5 (which is outdated for
several years). But now even 5.7 is out of support. I tried the update
advisor from mysqlsh: `util.checkForServerUpgrade();`. It threw several
"warnings", all about the illegal datetime default setting "0000-00-00".
Here's what the advisor said:
> It is strongly advised to replace zero values with valid ones, as they
may not work correctly in the future.
So as the warning appeared in 5.7.8 it's still ignored (or set to wontfix)
currently because of breaking ancient plugins.
It's a very BAD idea to have old MySQL releases with - partially massive -
security flaws in production use and IMHO a not so good idea to to ignore
the positive impact on security of the strict mode.
So PLEASE tell the community and the developers that there's a not so far
date in the future, where the faulty timestamp won't be accepted any
longer. The sentence "it will break several plugins" reminds me about: all
this damn compatibility stuff in Windoze - just to run ancient buggy
insecure old stuff.
With regards,
Peter.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/8857#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list