Issue upgrading Mahara site to 17.04dev
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Dmitrii Metelkin | ||
16.10 |
Fix Released
|
High
|
Unassigned |
Bug Description
This issue arose from bug #1647885. The upgrade fails because the primary key is incorrect in the table artefact_
Robert sayd: Rather than dropping and re-creating the table, it would be better to truncate the table and change the primary key. That way, the table structure stays the same.
To replicate:
1. Install 16.04 and go through the regular setup steps.
2. Upgrade to master
Expected result: The upgrade completes. Actual result: Upgrade fails on artefact.file with the following error message, which can only be seen when you attempt to run the upgrade again:
[DBG] 0e (artefact/
[DBG] 0e (lib/dml.php:157) postgres8 error: [-1: ERROR: multiple primary keys for table "artefact_
Command was: ALTER TABLE "artefact_
[WAR] 0e (lib/errors.
Call stack (most recent first):
log_
log_
SQLExceptio
execute_
xmldb_
upgrade_
Changed in mahara: | |
status: | Confirmed → In Progress |
no longer affects: | mahara/16.10 |
Changed in mahara: | |
status: | In Progress → Fix Committed |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
Patch for "16.10_STABLE" branch: https:/ /reviews. mahara. org/7368