Reviewed: https://reviews.mahara.org/2815 Committed: http://gitorious.org/mahara/mahara/commit/852254aa84038ecb787fb6920a8d8030ba4a9f41 Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch: 1.8_STABLE
commit 852254aa84038ecb787fb6920a8d8030ba4a9f41 Author: Robert Lyon <robe...@catalyst.net.nz> Date: Tue Nov 26 11:15:14 2013 +1300 Adding in missing keys & indexes Bug 1174623 For sites that have been upgraded from version 1.0 there are some missing constraints and indexes on the artefact_access_usr, artefact_access_role, artefact_attachment, group, grouptype_roles and view_autocreate_grouptype tables. Also some fields need to be adjusted to match the referenced field in another table so that they can be used as a foreign key Change-Id: Ifb8cd79d4fa9933be02f6086fb5dada18d47bfe2 Signed-off-by: Robert Lyon <robe...@catalyst.net.nz> Signed-off-by: Aaron Wells <aar...@catalyst.net.nz> -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1174623 Title: Correct schema drift during 1.0 -> 1.8 upgrades Status in Mahara ePortfolio: In Progress Status in Mahara 1.8 series: In Progress Status in Mahara 1.9 series: In Progress Bug description: We seem to get a lot of bug reports on the forum from people having issues after upgrading from pre-1.5 Mahara instances up to the latest. It seems that the upgrade scripts do not generate a database schema which is consistent with what you'd get from a clean 1.7 installation. If we want people to update to the latest version of Mahara (and we do!) then we need to make sure that the upgrade process works properly. So, we should test the upgrade process from each of the old versions of Mahara into master, and if it doesn't produce exactly the same DB schema as a fresh install, we need to correct the master upgrade scripts to solve this. Of course, there's also the matter of data in those tables getting messed up, but that's harder to recognize and fix. We could test for it partway, by making sure we upgrade a non-empty Mahara instance (something with at least a few users, pages, institutions, auth methods, etc). It might also be a good idea to add a tool that compares the schema against all of the install.xml files, so that users can tell whether they have a problem or not. Not worth writing one from scratch, but Moodle 2 has a script for copying a database, and one of its steps is to check the schema against all the XMLDB files, so we may be able to use that. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1174623/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
