[Building Sakai] Learning - Development Environment Setup Walkthrough

[Matthew Jones]

There are 'similar' issues that may have both been improved by MySQL 5.5.
However in MyISAM the index limitation was on the total of all the columns,
in InnoDB there were individual limits per column. [1] So it's *possible*
that this error could come up still in an InnoDB table, but it was much
less likely and in that case it would have been a bug.

However hibernate needed the correct dialect or it would try to create
tables in the default specified in the database configuration, which was
MyISAM until 5.5 when it was changed to InnoDB.

I've been running 5.5 locally on trunk without any problems, but haven't
tried it very much on 2.9. I believe there were a few minor issues that had
to be fixed in trunk and I still see a couple open issues like
https://jira.sakaiproject.org/browse/KNL-825
So it certainly hasn't had any significant QA or production runs on 5.5 yet.

[1] http://dev.mysql.com/doc/refman/5.1/en/innodb-restrictions.html


On Wed, Dec 5, 2012 at 9:51 AM, Mark J. Norton <markjnorton at earthlink.net>wrote:

>  The bug on the MySQL site indicated that it applied to both kinds of DB
> engines.
>
> - Mark
>
>
> On 12/5/2012 9:41 AM, Sam Ottenhoff wrote:
>
> I continue to use MySQL 5.1 with Sakai 2.9 and trunk.  Are you sure that
> you didn't have an InnoDB issue with your MySQL 5.1 install?  Did you
> confirm that the tables were being created using the InnoDB engine and not
> the MyISAM engine?
>
>
> On Wed, Dec 5, 2012 at 7:52 AM, Mark J. Norton <markjnorton at earthlink.net>wrote:
>
>>  >  Should #2 recommend MySql 5.5 instead of 5.1?
>>
>>  Interesting that this should come up just now.  I recently spent a day
>> trying to figure a problem I was getting on 2.9 startup.  The error read,
>>
>> com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Specified key was
>> too long; max key length is 1000 bytes
>>
>> Eventually, I tracked it down to Bug 4541<http://bugs.mysql.com/bug.php?id=4541>in MySQL.  It had to do with using UTF8.  Since UTF8 supports multibyte
>> characters, if a database is set up to use UTF8 (as Sakai is), then the
>> size of keys are tripled.  MySQL had a max key size of 1000 bytes, hence
>> the error message.  This bug wasn't fixed for close to EIGHT YEARS in
>> MySQL, but was eventually fixed in 5.5.  This came up because I was
>> installing 2.9 on a Debian machine and apt-get got me a 5.1 version of
>> MySQL.
>>
>> FWIW,
>> Mark Norton
>>
>>
>> On 12/4/2012 8:43 PM, Aaron Zeckoski wrote:
>>
>> On Tue, Dec 4, 2012 at 8:22 PM, Neal Caidin<nealcaidin at sakaifoundation.org> <nealcaidin at sakaifoundation.org> wrote:
>>
>>  Hey Aaron,
>>
>> Step 6 i. Configure tomcat 7 to use the old tomcat 5.5 classloader dirs .
>> Is that recommended?
>>
>>  Not only recommended but actually required.
>>
>>
>>  Should #2 recommend MySql 5.5 instead of 5.1?
>>
>>  The CLE team calls indicate that there has not been enough 5.5 testing
>> yet to recommend it.
>>
>>
>>  Should #4 have Maven 3 instead of 2.2?
>>
>>  I don't think so but I will leave it to others to comment. I use Maven 2.2.
>>
>> -AZ
>>
>>
>>
>>  On Dec 4, 2012, at 7:59 PM, Aaron Zeckoski <azeckoski at unicon.net> <azeckoski at unicon.net> wrote:
>>
>> Neal,
>> The docs refer to "Download and setup tomcat 7.0.21+ (stable only)"
>> already. What else do you think it should say?
>> -AZ
>>
>>
>> On Tue, Dec 4, 2012 at 1:29 PM, Neal Caidin
>>
>> P.S. I think the Confluence doc needs updating to reflect Tomcat 7 support,
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>
>>
>>
>> _______________________________________________
>> 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/20121205/d8660d43/attachment.html