db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Susan Cline (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-54) 'retain' was not a keyword, now it is, possible schema impact
Date Wed, 03 Nov 2004 23:41:32 GMT
'retain' was not a keyword, now it is, possible schema impact

         Key: DERBY-54
         URL: http://nagoya.apache.org/jira/browse/DERBY-54
     Project: Derby
        Type: Bug
  Components: SQL  
 Environment: not applicable
    Reporter: Susan Cline
    Priority: Minor

Versions prior to 5.1.60.x of Cloudscape did not have the 'retain' word as a reserved word.
 Versions after 5.1.60.x, including 10.0.2 have made the 'retain' word a reserved keyword.
 This impacts existing applications that used the 'retain' word in the schema.

Sysinfo output:

------------------ Java Information ------------------
Java Version:    1.4.2_05
Java Vendor:     Sun Microsystems Inc.
Java home:       C:\j2sdk1.4.2_05\jre
Java classpath:  C:\cs_home\105520~1.0_G\lib\derby.jar;C:\cs_home\105520~1.0_G\l
ib\derbytools.jar;C:\Apache\Tomcat 5.019\server\lib\catalina.jar;.;C:\IBM\SQLLIB
OS name:         Windows XP
OS architecture: x86
OS version:      5.1
Java user name:  slc
Java user home:  C:\Documents and Settings\Administrator
Java user dir:   C:\cs_home\10.0_GA\frameworks\embedded\bin
--------- Derby Information --------
[C:\cs_home\10.0_GA\lib\derby.jar] - (30301)
[C:\cs_home\10.0_GA\lib\derbytools.jar] - (30301)
[C:\IBM\SQLLIB\java\db2jcc.jar] 2.3 - (63)
[C:\IBM\SQLLIB\java\db2jcc_license_cisuz.jar] 2.3 - (63)
[C:\IBM\SQLLIB\java\db2jcc_license_cu.jar] 2.3 - (63)
----------------- Locale Information -----------------

Example of behaviour in 10.0.2:

ij> create table retain (i int);
ERROR 42X01: Syntax error: Encountered "retain" at line 1, column 14.

Prior to 5.1.60 (not sure exactly which release, but a 5.1 release) this create table statement
would have succeeded.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message