Skip to:

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

Clean up VARCHAR2 BYTE/CHAR discrepancies in 2.8.0 Oracle conversion script

Description

In the Oracle conversion scripts, we need to specify that a particular column's varchar2 length is based on CHARs instead of BYTEs to ensure consistency with the auto-ddl'd versions.

is depended on by

Activity

Show:

Seth Theriault March 17, 2011 at 7:22 AM

Tested and working.

Hudson CI Server March 16, 2011 at 10:09 PM

Integrated in sakai trunk #466 (See http://builds.sakaiproject.org:8080/job/sakai%20trunk/466/)
resolve VARCHAR2 BYTE/CHAR discrepancies in 2.8.0 Oracle conversion script

Seth Theriault March 16, 2011 at 9:23 PM

Merged to 2.8.x, r89894.

Seth Theriault March 16, 2011 at 9:01 PM

Committed to trunk, r89893.

Seth Theriault February 24, 2011 at 5:36 PM

For example, we need to fix this sort of thing:

– PROFILE_MESSAGES_T.FROM_UUID
2.8 auto.ddl: VARCHAR2(99 CHAR)
2.7.1 converted: VARCHAR2(99 BYTE)

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Conversion Script Required

Yes

Environment

Oracle 9i
Created February 24, 2011 at 5:35 PM
Updated March 27, 2012 at 7:02 AM
Resolved March 17, 2011 at 7:22 AM