Wordpress Database Update reports errors but says it's successfull

[hakre]

I just updated my database on current HEAD of trunk by pressing the button while WP told be to do so. I got an error reported:

---

WordPress database error: [Out of range value adjusted for column 'post_parent' at row 4]
ALTER TABLE wp_posts CHANGE COLUMN post_parent post_parent bigint(20) unsigned NOT NULL default '0'

---

However right beneath of it, I was greeted with:

---

Update Complete

Your WordPress database has been successfully updated!

---

First of all I ask myself if I can trust that message as an error has been reported.

Then this looks like that the update is not compatbile with my MySQL server which is 5.0.19 and matching the ​wordpress system requirements on the webpage (which seems to be out of date for trunk, but, well 5.0 is required according to version.php).

Related: #3112

[dd32]

The Database error shouldn't be occurring, however it saying everything is hunky-dory when it's not is indeed a bit of a bug. Its worth noting that for 99.9% of users, They'll never come across an issue with the schema updates, It'll only be the small number of installs which are either locked down (so Alter/Create doesnt work) or those with altered non-standard database table layouts (ie. plugin renamed a field or something equally as crazy)

For reference, The SQL there is updating it to an unsigned bigint, from [10852] (or failing that [2629]...), so not a recent addition, nor a breaking addition. In your case, You'll probably find you've got a negatively signed post parent or something such as that..

[hakre]

Weird. I was updating on a trunk-near test system, at least this was not older than let's say about two or three month, at least I had 3.1-trunk running on it, nothing 2009. I have another trunk on that system and will give it a test.

[hakre]

The other blog didn't had the issue, but for the one with the error I found a negative post id in post_parent: -1207602599. Sort of wired as the highest post id is 257 and this is just a test system with very little content.

[c3mdigital]

hakre,

Can you still confirm this error upgrading to 3.6 or trunk on MySQL 5.0?

Is this something that we still need to fix?

[SergeyBiryukov]

Appears to be an edge case. We could probably fix displaying of the success message if there are errors, I'd suggest creating a new ticket for that.