mahara-contributors team mailing list archive

[Stacey Walker <stacey@xxxxxxxxxxxxxxx>]

I have been able to upgrade from fresh installs of 1.2.3 and 1.2.5 to
1.3.3 without problems so there is a possibility that the dumps have
some partially corrupt data in them.

The upgrades did take a bit of time to get past core so if this was
interrupted on a mysql database then it could have left the database in
an inconsistent state; due to the lack of DDL transactional support in
mysql.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/728837

Title:
  Upgrade broken from 1.2.6 to 1.3.0

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Michele Balazs reported the following error when trying to upgrade her
  site from 1.2.3 to 1.3.3:

  Could not execute command: ALTER TABLE mah_artefact ADD CONSTRAINT mah_arte_aut_fk FOREIGN KEY (author) REFERENCES mah_usr (id)
  Call stack (most recent first):

      * execute_sql("ALTER TABLE mah_artefact ADD CONSTRAINT mah_arte_a...", true) at/srv/www/mahara/lib/dml.php:1406
      * execute_sql_arr(array(size 1), true, true) at /srv/www/mahara/lib/ddl.php:972
      * add_key(object(XMLDBTable), object(XMLDBKey)) at/srv/www/mahara/lib/db/upgrade.php:1487
      * xmldb_core_upgrade("2009111010") at /srv/www/mahara/lib/upgrade.php:301
      * upgrade_core(object(stdClass)) at /srv/www/mahara/admin/upgrade.json.php:93

  She was also able to narrow it down to the upgrade between 1.2.6 and
  1.3.0 (thanks Michele!).

  mysql: 5.0.67
  php: 5.2.12

  See forum thread:
  http://mahara.org/interaction/forum/topic.php?id=2884