mahara-contributors team mailing list archive

[Mahara Bot <1243525@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2645
Committed: http://gitorious.org/mahara/mahara/commit/05a25eab83894c4a7241f4badf828302c56208d3
Submitter: Son Nguyen (son.nguyen@xxxxxxxxxxxxxxx)
Branch:    master

commit 05a25eab83894c4a7241f4badf828302c56208d3
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Wed Aug 14 15:40:21 2013 +1200

Remove "TYPE=INNODB" (incompatible with MySQL 5)

Bug 1243525: Also, since it was only used in the pre-1.1 upgrade section, it's no
longer necessary to define this at the top of upgrade.php at all

Change-Id: I907467f2ffd80844fe7f3f35eeb92a51a40ad7dd

-- 
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/1243525

Title:
  Issues with 1.0->1.8 upgrade path

Status in Mahara ePortfolio:
  In Progress

Bug description:
  See also https://bugs.launchpad.net/mahara/+bug/1238407 (ENGINE=INNODB)
  and https://bugs.launchpad.net/bugs/1174623 (Correct schema drift)

  Since the README still says you can upgrade from 1.0 to master, I
  tested it out prior to the 1.8.0 release. I found a couple of
  problems, which I'll track here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1243525/+subscriptions