[Building Sakai] 2.9.0 DB Conversion, MySQL script error

[Gast, Cynthia (cmw6s)]

My apologies, Sam, I should have first researched whether the LTI SQL issue had already been reported.  Thank-you for the information.

Yes, we use the official releases because they have been QA'd and considered ready for production.  We are getting familiar with 2.9.0 and beginning some of the many local changes we make; we are intending to move to 2.9.1 once it is released.

Thanks again,
Cindy


________________________________
From: Sam Ottenhoff [ottenhoff at longsight.com]
Sent: Thursday, January 24, 2013 12:11 PM
To: Gast, Cynthia (cmw6s)
Cc: sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] 2.9.0 DB Conversion, MySQL script error

Please don't file another JIRA issue!  It's already been reported, fixed, and merged into 2.9.x.

Do you have a specific reason for using the 2.9.0 release tag instead of the 2.9.x maintenance branch?  If you only want to deal with official releases, you will get 100+ Sakai bug fixes by waiting for the 2.9.1 official release.

--Sam


On Thu, Jan 24, 2013 at 12:08 PM, Gast, Cynthia (cmw6s) <cmw6s at eservices.virginia.edu<mailto:cmw6s at eservices.virginia.edu>> wrote:
Thanks, Sam, will-do :-)

FYI, found another 2.9.0 MySQL DB conversion script bug, for LTI tables.  3 create-table statements are not terminated with a ';' so when I ran the conversion script, I received an error after a 4th create-table (SST_SERVERSTATS) statement, and none of the 4 tables were created.  Tables involved: lti_mapping, lti_content, lti_tools, and then SST_SERVERSTATS (which is terminated with ';').  See BLTI-156 sql, then STAT-315 sql, in the script: sakai_2_9_0_mysql_conversion.sql.

I will file a new JIRA for this LTI issue also.

Cindy

________________________________
From: Sam Ottenhoff [ottenhoff at longsight.com<mailto:ottenhoff at longsight.com>]
Sent: Thursday, January 24, 2013 11:19 AM
To: Gast, Cynthia (cmw6s)
Cc: sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>

Subject: Re: [Building Sakai] 2.9.0 DB Conversion, MySQL script error



Unsure if this has been reported.  If not, should SAK-22700 or SAK-16091 be re-opened, or a new issue opened?

Attaching the adjusted script, which runs without error after editing the table name.

Re-opening old, merged, and verified issues is really confusing.  Opening a new JIRA and linking the new JIRA to the problematic ticket is preferred.

And yes, your bug is legitimate.  Please file a new issue.

Thanks,
Sam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130124/74dd02e5/attachment.html