Yes, timedate default is 0000–00-00. See
I do not recommend changing the database setup.
Thanks. The reason I asked is that the upgrade checker utility for upgrading to MySQL 8.0 flagged that as a warning because MySQL 8.0 is by default, in strict mode and if the timedate column in the tables are left at 0000–00-00, it may cause problems with the database when upgraded and I can’t take chances with that. The MySQL documentation suggests as one solution, to set that to a value of either NULL , or a numerical value. There is an option to set it for current_timestamp, and I wondered if setting that value to either NULL, or current_timestamp would cause issues with the database. So you are saying that I can change that value to NULL, or current_timestamp and it will be ok? Either of those values removes the warning in the upgrade checker utility report.
I’m saying to ignore what MySQL i s saying and leave the database as it is. It’s what WP is expecting and works just fine with MariaDB 10.
Ah, ok, thanks. That’s what I was most worried about. You’ve been very helpful. Thanks. I use WooCommerce also, so now I have to find out if it will impact that at all.
Actually, I just realized that WooCommerce creates tables in the WP databases so it should not be a problem, I don’t think.
Craig
- This reply was modified 1 hour, 2 minutes ago by .