mahara-contributors team mailing list archive

[Mahara Bot <1180243@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2270
Committed: http://gitorious.org/mahara/mahara/commit/5ac7a34daf4f96994c6fa576ad2420e396cb04ed
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    1.5_STABLE

commit 5ac7a34daf4f96994c6fa576ad2420e396cb04ed
Author: Son Nguyen <son.nguyen@xxxxxxxxxxxxxxx>
Date:   Mon May 20 12:33:39 2013 +1200

Fix InnoDB verification issue for MySQL 5.6 (Bug #1180243)

Use the command 'SHOW ENGINES' instead of 'SHOW VARIABLES'
See also:
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_have_innodb

Change-Id: Iee3ff04384f9115ceb7af3c7d852899efbd1d4de
Signed-off-by: Son Nguyen <son.nguyen@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1180243

Title:
  Installation hangs with "Mahara requires InnoDB tables. Please ensure
  InnoDB tables are enabled in your MySQL server."

Status in Mahara ePortfolio:
  Confirmed
Status in Mahara 1.5 series:
  Confirmed
Status in Mahara 1.6 series:
  Confirmed
Status in Mahara 1.8 series:
  Fix Committed

Bug description:
  Fresh install 1.7.1 on OSX Server 10.7.5
  MySQL 5.6.11 - MySQL Community Server 
  Chrome 26.0.1410.65

  My MySQL Installation works flawlessly with some other products like moodle 2.5.
  Any new tables created with the mahara user via phpMyAdmin are InnoDB tables, 

  show engines;

  gives

  InnoDB,DEFAULT,Supports transactions, row-level locking, and foreign
  keys,YES,YES,YES.

  So how to continue?

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