Inconsistencies in Samigo column sizes after applying Sakai 2.8.0 Oracle conversion scripts
GENERAL
TESTING
GENERAL
TESTING
Description
is depended on by
Activity
Show:

Hudson CI Server February 23, 2011 at 9:10 PM
Integrated in sakai trunk #447 (See http://builds.sakaiproject.org:8080/job/sakai%20trunk/447/)

Hui Tsao February 22, 2011 at 11:30 AM
Hi Seth,
Thanks for finding this issue. I have updated the conversion scripts to match with the auto ddl. Please review them if you want.
Thanks,
Karen
When comparing a fresh auto-ddl'd 2.8 beta05 database against an upgraded 2.7.1 database, the following inconsistencies were found:
SAM_ASSESSFEEDBACK_T.FEEDBACKCOMPONENTOPTION
2.8 auto.ddl: NUMBER(10,0)
2.7.1 converted: NUMBER(22,0)
-SAM_PUBLISHEDFEEDBACK_T.FEEDBACKCOMPONENTOPTION
2.8 auto.ddl: NUMBER(10,0)
2.7.1 converted: NUMBER(22,0)
The relevant entries in the 2.8 conversion scripts are:
–
alter table SAM_ASSESSFEEDBACK_T add FEEDBACKCOMPONENTOPTION number default null;
update SAM_ASSESSFEEDBACK_T set FEEDBACKCOMPONENTOPTION = 2;
alter table SAM_PUBLISHEDFEEDBACK_T add FEEDBACKCOMPONENTOPTION number default null;
update SAM_PUBLISHEDFEEDBACK_T set FEEDBACKCOMPONENTOPTION = 2;