[Building Sakai] 2.8.0 mysql conversion script issues

[Matthew Jones]

Agreed, this is what both of your problems are. OSX has the wrong option for
table names (which is why the conversion is having a problem with the table
case), and the tables weren't created with InnoDB. (Which is why it's having
a problem with the "too long")

The option for table names and a conversion script is described here. I know
the InnoDB option is somewhere in the installation guide but don't see it at
the moment. I'm not sure if there's a conversion for that.

https://confluence.sakaiproject.org/display/DOC/Sakai+Admin+Guide+-+Database+Configuration+and+Tuning

-Matthew

On Fri, Apr 15, 2011 at 9:22 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> Questions
>
> 1.  What version of MySQL are you using?
> 2.  What is your storage engine type?  If not InnoDB, change it to InnoDB.
>  The Sakai CLE requires transaction support.
> 3.  What OS?
>
> In most varieties of UNIX, MySQL is case sensitive since the underlying
> operating system determines the case sensitivity of database and table
> names.  This is not the case for MySQL running in Windows, which is not case
> sensitive.  Previous MySQL conversion scripts contained a mixture of upper
> case and lower case statements which occasionally caused problems for
> upgraders; for 2.8 we opted for lower case for the syntax while leaving the
> table and field names upper case.  Testing on MySQL 5.1 did not reveal any
> issues with that choice.
>
> Anyways, report back on the specifics of your MySQL installation.  We need
> more info before we can begin to diagnose your reported problem
>
> Probably unrelated to your issue but users upgrading from MySQL 5.0 to
> MySQL 5.1 on a Mac have reported name comparison problems on startup.  This
> issue was solved by specifying the following property in a local my.cnf
> configuration file:
>
> lower_case_table_names=1
>
> A minimalist example:
>
> [mysqld]
> default-storage-engine=InnoDB
> lower_case_table_names=1
>
> For more info on this issue see
> http://collab.sakaiproject.org/pipermail/sakai-dev/2010-June/008066.html
>
> Cheers,
>
> Anthony
>
> On Apr 15, 2011, at 8:05 AM, Theodoros Theodoropoulos wrote:
>
> > Again, in sakai_2_8_0_mysql_hbm_indexes.sql, in the first line,
> > "sakai_message_bundle" for the same reason, probably needs to be
> > capitalized...
> >
> >> Hello devs,
> >>
> >> This is my second post in this forum and after some time of playing
> >> around with the program, I still have very limited knowledge of
> >> sakai-internals, but trying to upgrade my local 2.7.1 test sakai to the
> >> not-yet-announced 2.8.0, I found the following a couple of issues with
> >> sakai_2_8_0_mysql_conversion.sql.
> >>
> >> First, It seems that the index creation for SAKAI_MESSAGE_BUNDLE should
> >> be capitalized: "create index SMB_SEARCH on SAKAI_MESSAGE_BUNDLE
> >> (BASENAME, MODULE_NAME, LOCALE, PROP_NAME);" instead of
> >> "create index SMB_SEARCH on sakai_message_bundle (BASENAME, MODULE_NAME,
> >> LOCALE, PROP_NAME);"
> >>
> >> But even then, the sql script produces the error "ERROR 1071 (42000):
> >> Specified key was too long; max key length is 1000 bytes" (I'm running
> >> mysql 5.0.77). This is listed here as a mysql-bug:
> >> http://bugs.mysql.com/bug.php?id=4541 (not solved 7 years after it has
> >> been detected),or as seen later in the post, as a bad practice.
> >>
> >> In either way, it is a blocker for the upgrade. Can you verify/reproduce
> >> it? Or is it something with my installation that messes things up?
> >>
> >> Best regards,
> >> Theodoros
> >>
> >> PS. I understand that the upgrade procedure documentation is not yet
> >> published, so if you're going to describe a solution there, please
> >> accept my apologies for being impatient :) Keep up the good work!
> >> _______________________________________________
> >> 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"
> >>
> >
> > _______________________________________________
> > 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"
> >
> >
>
>
> _______________________________________________
> 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"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110415/7c862056/attachment.html