Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Inconsistencies in ETS column types after applying Sakai 2.8.0 Oracle conversion scripts

Description

When comparing a fresh auto-ddl'd 2.8 rc02 database against an upgraded 2.7.1 database, the following column-type inconsistencies were found:

– EMAIL_TEMPLATE_ITEM.EMAILFROM
2.8.0 auto.ddl: CLOB
2.7.1 converted: VARCHAR2(255 BYTE)

Activity

Show:

Anthony Whyte March 29, 2011 at 6:58 PM

MySQL conversion scripts also updated.

trunk r90892; 2.8.x r90895.

Anthony Whyte March 21, 2011 at 4:43 AM

ets-0.5.x, r90112.

Hudson CI Server March 21, 2011 at 4:19 AM

Integrated in emailtemplateservice trunk (build and deploy) #269 (See http://builds.sakaiproject.org:8080/job/emailtemplateservice%20trunk%20(build%20and%20deploy)/269/)
changed type from text to java.lang.String

David Horwitz March 21, 2011 at 4:08 AM

fixed with r90110

Seth Theriault March 16, 2011 at 5:16 AM

The "type="text"" attribute is probably causing the creation of a CLOB. If it were more like TEMPLATE_KEY, it would be a varchar2(255).

Although it's not a problem, I think we should be consistent so once again the choice is: modify the hbm or modify the conversion?

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Conversion Script Required

Yes

Environment

Oracle9i
Created March 15, 2011 at 1:34 PM
Updated March 29, 2011 at 8:44 PM
Resolved March 21, 2011 at 4:08 AM