mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #01217
[Bug 622763] Re: Cannot upgrade 1.1.x to 1.2.x due to artefact_file_files not being upgraded in correct order
** Changed in: mahara
Status: Fix Committed => Fix Released
--
Cannot upgrade 1.1.x to 1.2.x due to artefact_file_files not being upgraded in correct order
https://bugs.launchpad.net/bugs/622763
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Status in Mahara ePortfolio: Fix Released
Bug description:
Two additional fields are added into the artefact_file_files table in file artefact/file/db/upgrade.php at the following version points...
2008101602 => field 'filetype' is added
2008091100 => field 'fileid' is added
Unfortunately these fields are accessed within the core upgrade script lib/db/upgrade.php. At version point 2009111012 an sql query is run on artefact_file_files accessing the filetype field.
As in an upgrade the core is always upgraded before anything else, if the starting database is old enough (any 1.1.x version I think) then core upgrade will attempt to access fields that do not (yet) exist causing a fatal error and upgrading failing.
References