Skip to end of metadata
Go to start of metadata

1.0 Database Conversions

Unable to render {include} The included page could not be found.

1.1 Database Conversion Script Corrections

Update SAKAI_SITE_TOOL table to replace sakai.assignments with sakai.assignments.grade in Mercury site ( SAK-14482 - Mercury site has old assignments tool ( Closed) )

The "mercury" site includes the old sakai.assignment tool which has been deprecated since the release of Sakai 2.5.0. The conversion scripts below replace it with the current sakai.assignment.grades tool.

2.6.0 to 2.6.1 conversion scripts update, 19 Oct 2009 ( SAK-17219 - Conversion script for 2.6.1 is slow to run on large assignment data sets and should be improved ( Closed) , SAK-1654 - This site XYZ is not available for editing right now ( Closed) )

Matt Jones of the University of Michigan reports that the original 2.6.0 to 2.6.1 conversion script that operates on assignment_content table "is inefficient, potentially locks tables and performs too many scans, especially if there are hundreds of thousands of rows." Matt has revised both the MySQL and Oracle conversion scripts to improve their performance.

Assignments conversion script column conversion change, 1 Sept 2009 ( SAK-16668 - assignments / private notes and model answers does not display proper error message for text over 255 characters ( Closed) )

(minus) Assignments / private notes and model answers do not display proper error message for text over 255 characters. If you upgraded to Sakai 2.6.0 PRIOR TO 1 September 2009 you must run the following column conversion. You should check your columns as they should be converted from varchar to text (or just run the conversion anyway as it is safe to rerun, which is why they are uncommented).

-- SAK-16668
-- Note: If you upgraded to sakai 2.6.0 PRIOR TO September 1st 2009 you'll need to run this column conversion.
-- You should probably check your columns as they should be converted from varchar to text
-- (Or just run them anyway as it is safe to rerun, which is why they are uncommented)
ALTER TABLE ASN_MA_ITEM_T CHANGE TEXT TEXT TEXT;
ALTER TABLE ASN_NOTE_ITEM_T CHANGE NOTE NOTE TEXT;

2.6.0 conversion script update, 22 July 2009 ( SAK-16751 - Comment out site.add.course backfill SQL ( Closed) )

(minus) John Leasia of the University of Michigan reports an issue with the 2.6.0 conversion scripts with respect to the new permission site.add.course. Currently, the conversion script adds site.add.course to the user account template realms with a .auth role (good) but also "backfills" and adds the permission to other templates since the backfill SQL filters on all realms with a .auth role. The account template realms are all that should be updated since these templates are used for all accounts associated with the template (all registered accounts, all sample accounts, etc.). Since users do not have their own realm that determines whether or not they can add a site or add a course site backfilling is unnecessary and adding site.add.course to all template realms with a .auth role may not square with an institution's permission strategy.

We have commented out this portion of the script and committed the changes to trunk and the 2.6.x maintenance branch. We recommend that users run the updated 2.6.x conversion scripts.

2.6.x

MySQL

sakai_2_6_0_mysql

2.6.x

Oracle

sakai_2_6_0_oracle

1.3 Other Database Conversions

Sakai 2.6 also includes data and schema conversions outside the standard scripts to address data integrity issues for assignments, content hosting and email archive. Below is a quick summary and overview of the process for each tool.

1.3.1 Email Archive performance improvements

Unable to render {include} The included page could not be found.

1.3.2 Assignments Tool

Unable to render {include} The included page could not be found.

1.3.3 Content Hosting

Unable to render {include} The included page could not be found.

2.0 sakai.properties changes

Unable to render {include} The included page could not be found.

3.0 Deprecated Discussion Tool

Unable to render {include} The included page could not be found.
  • No labels