NULL values in database queries
There seems to be an issue with the migration part of the new 3.0.0 updated. We are seeing this issue across many sites and servers.
When the update happens, it is calling:
This then calls:
$cpt_id = $prli_link->create_cpt_for_link($link->name, $link->created_at, $link->updated_at);
The problem is that at least in our examples, every entry in the
wp_prli_linkstable has an
updated_atvalue of NULL. The
create_cpt_for_linkfunction then tries to do a direct insert to the
wp_poststable except the values for
post_modified_gmtrespectively come out like so:
NULL, '1970-01-01 00:00:00'
This is not allowed by the
WordPress database error Column 'post_modified' cannot be null for query...
This causes a lot of spam in error logs (in fact we’ve seen it creating 10+GB of error logs quite easily) and also causes load on the database. It then seems to keep trying every 30 minutes due to the transient you have to retry installations.
A fix for this problem ASAP would be very useful.
- The topic ‘NULL values in database queries’ is closed to new replies.