Last modified: 2011-08-26 00:58:49 UTC
Looking at trying to fixup r90668, just trying to add a really simple campaign. Selected "Test" and then just pressed next on the next window... A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: INSERT INTO `mw_uw_campaign_conf` (cc_campaign_id,cc_property,cc_value) VALUES ('1','skipTutorial','') from within function ‘DatabaseBase::insert.’ Database returned error ‘1062: Duplicate entry '1' for key 'PRIMARY' (localhost).’
What does this have to do with r90668? Also, I don't understand the steps to reproduce. > then just pressed next on the next window... Do you mean "pressed back"? That was fixed by my recent commits.
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: INSERT INTO `mw_uw_campaign_conf` (cc_campaign_id,cc_property,cc_value) VALUES ('4','skipTutorial','') from within function ‘UploadWizardCampaign::writePropsToDB.’ Database returned error ‘1062: Duplicate entry '4' for key 'PRIMARY' (localhost).’ Nope. Visit Special:UploadCampaigns Enter a campaign name, press add, then on the page just press submit You'll get the error above Raymond is experiencing the same issue
(In reply to comment #2) > > Raymond is experiencing the same issue Not the same. Mine was bug 30554. I was able to save :)
*** This bug has been marked as a duplicate of bug 30554 ***
So if it's not the same, why mark it as duplicate? In any case, I cannot reproduce this.
It is the same issue, its an I can reproduce on demand... Have the tables been updated since they were added. It seems to also do an insert when editing, so hence duplicate key
I don't see anything wrong. Maybe you got your wiki into a messed up state somehow before the fix was made, and are seeing the effects of that?
Can you try reproduce on another wiki?
(In reply to comment #7) > I don't see anything wrong. Maybe you got your wiki into a messed up state > somehow before the fix was made, and are seeing the effects of that? Dropping the tables and recreating them seems to have fixed it. Mehhhh
Yes -- if you had installed this extension before, it incorrectly marked a certain field as being UNIQUE. Dropping the table and running update.php fixes it.
Really? What index was this?
