Last modified: 2013-03-01 09:24:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T47151, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45151 - Upgrading SMW 1.8.0 to 1.8.0.2. SMW_setup.php throws an error.
Upgrading SMW 1.8.0 to 1.8.0.2. SMW_setup.php throws an error.
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
master
All All
: Unprioritized major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-19 14:45 UTC by Neill Mitchell
Modified: 2013-03-01 09:24 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Neill Mitchell 2013-02-19 14:45:49 UTC
Hi.

I've just upgraded a SMW 1.8.0 instance to 1.8.0.2.

When I run SMW_setup.php I get the following errors:

Selected storage "SMWSQLStore3" for update!

Setting up standard database configuration for SMW ...

Selected storage engine is "SMWSQLStore" (or an extension thereof)

Checking table `smw_object_ids` ...
    Table already exists, checking structure ...
    ... changing type of field smw_id from 'INT(8) UNSIGNED NOT NULL KEY 
AUTO_INCREMENT' to 'INT(8) UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT' 
... A database error has occurred.  Did you forget to run 
maintenance/update.php after upgrading?  See: 
https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script
Query: ALTER TABLE `smw_object_ids` CHANGE `smw_id` `smw_id` INT(8) 
UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT FIRST
Function: SMWSQLHelpers::updateMySqlField
Error: 1068 Multiple primary key defined (localhost)

I have run update.php. That throws the same error. This has happened on 
two instances now.
Comment 1 Neill Mitchell 2013-03-01 09:24:29 UTC
Fixed with 1.8.0.3.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links