[Deploying Sakai] 2.6.0-2.6.1 mysql conversion
thall at brocku.ca
Mon Oct 26 08:31:21 PDT 2009
Thanks, I do have the DB to be case sensitive. I changed the table names
in the script to be upper case and it ran fine. I have seen other systems
with two different tables depending upon case sensitivity for proper
system operation so I always ask before making that change.
On Mon, 26 Oct 2009, Matthew Jones wrote:
> This probably is related to case sensitivity of the table names. I was
> testing this on a mysql running on windows which doesn't have
> distinction for case. I was just talking to Noah and he said likely,
> unless you'd had options set, the table names need to be in upper case
> for sakai tables.
> Try making both of the lowercase table names in the script
> (assignment_submission, assignment_submission_id_temp) into uppercase
> names (ASSIGNMENT_SUBMISSION,ASSIGNMENT_SUBMISSION_ID_TEMP) and see if
> that fixes it.
> On Mon, Oct 26, 2009 at 10:44 AM, Tom Hall <thall at brocku.ca> wrote:
> > Good Day Everyone
> > I have just built ans started to test 2.6.1 on our development system.
> > When I attempted to run the sakai_2_6_0-2_6_1_mysql_conversion.sql upgrade
> > script I got the following error repeated 16 times.
> > ERROR 1146 (42S02): Table 'sakai26.assignment_submission' doesn't exist
> > corresponding to the internationization fix in the assignment_submission
> > talbe.
> > This table does not exist on any of our systems. Are we missign something
> > or is that part of an optional module/tool?
> > Thanks
> > Tom
> > _______________________________________________
> > production mailing list
> > production at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/production
> > TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
More information about the production