[Building Sakai] Mysql Converston script 2.7.1 to 2.8.0

[Theodoros Theodoropoulos]

Hello Nico,

I had the same problem, and the issue was that SOME of my sakai tables
were left in MyISAM instead of INNODB. You must find which tables are
still in MyISAM and converted them to INNODB (using ALTER TABLE ...)
Also, make sure you have "default-storage-engine=InnoDB" in your cnf
file for the new tables.
In addition to that, I had also omitted the lower_case_table_names=1 in
my.cnf, but if you're running on Windows, it should not be a problem.
Both settings are described in
https://confluence.sakaiproject.org/display/DOC/Sakai+CLE+2.8+Release+Notes
, paragraph 5.x

Best regards,
Theodoros

On 28/4/2011 12:31 μμ, Coetzee, Nico wrote:
> This message (and attachments) is subject to restrictions and a disclaimer. Please refer to http://www.unisa.ac.za/disclaimer for full details.
>
> Hi
>
> I have a problem with the mysql conversion script for sakai 2.8.0.
>
> on line 279 it tries to create a index but if fails.
>
> mysql>   create index SMB_SEARCH on SAKAI_MESSAGE_BUNDLE (BASENAME, MODULE_NAME, LOCALE, PROP_NAME);
> ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
>
> Can some one please help
>
> Nico Coetzee
> Designer Developer
> ICT
> Unisa Main Campus
> Preller Street
> Pretoria
> Tel: +27 (012) 429-4661
> Fax : 0862756913
>
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"