Sorry folks, but this is bugging me now.
Why is WP's database code so goofy that it won't work if MySQL 5 is in strict-mode? All my reading on the topic strongly suggests that all strict-mode really does is throw errors instead of warnings, and all of the errors I've actually seen seem to involve the fact that fields that are required aren't given default values and don't have values explicitly inserted. How the hell did this get past Q/A anyways? Didn't anyone realize that the database code was severely cracked, if not actually broken?
As an example, the problems that WP is having with strict-mode would be impossible if it used SQL Server. There is no sloppy-mode in SQL Server. There is no sloppy-mode in Oracle for that matter.
Why is WordPress among the hundreds of other PHP apps that break when the database suddenly starts enforcing the rules (rules that haven't changed appreciably since 4.0)?
Will this be fixed for the 2.0 release?