[wp-trac] [WordPress Trac] #8857: Make WP MySQL strict mode compliant

WordPress Trac noreply at wordpress.org
Mon Nov 9 22:41:12 UTC 2020


#8857: Make WP MySQL strict mode compliant
-------------------------+----------------------
 Reporter:  ghostks      |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  lowest       |   Milestone:
Component:  Database     |     Version:  2.7
 Severity:  minor        |  Resolution:  wontfix
 Keywords:               |     Focuses:
-------------------------+----------------------
Changes (by helen):

 * status:  reopened => closed
 * resolution:   => wontfix


Old description:

> Incorrect Mysql scheme during Wordpress installation on DBMS with strict
> date/datetime format settings will result in errors and will be unable to
> finish succesfully. Existing default date and datetime values are
> '0000-00-00' and '0000-00-00 00:00:00' which are not supported any more.
> Please see official Mysql dev documentation for more information:
>
> {{{
> The DATE type is used when you need only a date value, without a time
> part. MySQL retrieves and displays DATE values in 'YYYY-MM-DD' format.
> The supported range is '1000-01-01' to '9999-12-31'.
> }}}
> http://dev.mysql.com/doc/refman/5.0/en/datetime.html

New description:

 Incorrect Mysql scheme during WordPress installation on DBMS with strict
 date/datetime format settings will result in errors and will be unable to
 finish succesfully. Existing default date and datetime values are
 '0000-00-00' and '0000-00-00 00:00:00' which are not supported any more.
 Please see official Mysql dev documentation for more information:

 {{{
 The DATE type is used when you need only a date value, without a time
 part. MySQL retrieves and displays DATE values in 'YYYY-MM-DD' format. The
 supported range is '1000-01-01' to '9999-12-31'.
 }}}
 http://dev.mysql.com/doc/refman/5.0/en/datetime.html

--

Comment:

 @nsinelnikov As noted in the discussion in Slack, this is valid in non-
 strict mode, which we have to keep for what essentially boils down to
 back-compat reasons. If documentation needs to be updated, that is fine,
 we just don't need this ticket open because there is nothing actionable
 for core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/8857#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list