[wp-hackers] SQL Error on upgrading to 1.3

[Peter Westwood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Omry Yadan wrote:
> Sounds like a potentially serious bug.
> 
> better open a bug report at the trac site.
> 
> it's best if you have the of the blog database dump (from before the
> upgrade) ready to be handed to the developer in charge of this to allow
> easy reproduction of the bug.
> 
> (it's probably not the best idea to attach this to the ticket, it may
> contain sensitive information).
> 
> 
> Swaroop Hegde wrote:
> 
>> Same here.
>>
>> Is it fine to continue with the upgraded blog?
>>
>> Sincerely,
>>
>> Swaroop Hegde
>> www.swaroophegde.com
>>
>> -----Original Message-----
>> From: Ozh [mailto:ozh at planetozh.com] Sent: 26 September 2007 14:05
>> To: wp-hackers at lists.automattic.com
>> Subject: [wp-hackers] SQL Error on upgrading to 1.3
>>
>> Ola there
>>
>> On 3 of my blogs (either real or test blogs) I've upgraded to 1.3 and
>> during upgrade.php?step=1 I've alwyas had notices like :
>>
>> WordPress database error: [Duplicate entry '106-14' for key 1]
>> INSERT INTO wp_term_relationships (object_id, term_taxonomy_id) VALUES
>> ('106', '14')
>>
>> WordPress database error: [Duplicate entry '106-14' for key 1]
>> INSERT INTO wp_term_relationships (object_id, term_taxonomy_id) VALUES
>> ('106', '14')
>>
>> WordPress database error: [Duplicate entry '106-14' for key 1]
>> INSERT INTO wp_term_relationships (object_id, term_taxonomy_id) VALUES
>> ('106', '14')
>>
>> Then, the usual message that upgrade is complete and I can click
>> Continue. Nothing seems to be broken past this point, I don't seem to
>> have lost any category or anything.
>>
>> Any pointer of what I should check before upgrading ?
>>

- From Ryan (on wp-testers):
- ----
Duplicate entry errors when inserting into the term_relationships
table should not cause any harm.  WP 2.2 did not enforce the post_id,
category_id relationship to be unique in the post2cat table.  That has
resulted in some people having multiple rows for the same post_id,
category_id pair in post2cat, as Alexander described.  The upgrade is
incorrectly assuming that the post2cat rows are unique.  This will
result in the db error messages but should not mess up your upgrade.
- ----

I believe this explains what you are seeing.

westi
- --
Peter Westwood
http://blog.ftwr.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG+iVLVPRdzag0AcURAuZ7AJsESpmxbusiLiYbLUMlAMv8QPqy4gCgtRVc
kFSFCwp9u7puTuUbht1DDCU=
=xS71
-----END PGP SIGNATURE-----