db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5254) The keywords introduced by the CREATE SEQUENCE work are treated as reserved rather than unreserved.
Date Tue, 31 May 2011 19:09:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-5254:

    Attachment: derby-5254-01-aa-unreserveKeywords.diff

Attaching derby-5254-01-aa-unreserveKeywords.diff. This patch makes the CYCLE, MINVALUE, and
MAXVALUE unreserved keywords. I am running regression tests now.

Touches the following files:


M      java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj

Adds CYCLE, MINVALUE, and MAXVALUE to the nonReservedKeywords() production.


M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/SequenceTest.java

Adds a test case to verify that you can now create columns with these names.

> The keywords introduced by the CREATE SEQUENCE work are treated as reserved rather than
> ---------------------------------------------------------------------------------------------------
>                 Key: DERBY-5254
>                 URL: https://issues.apache.org/jira/browse/DERBY-5254
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:,,,
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-5254-01-aa-unreserveKeywords.diff
> The following keywords appear in the non-reserved keywords list in sqlgrammar.jj but
are not included in nonReservedKeyword() production further down in that file. The intention
was for the following words to be non-reserved keywords. But they are treated as reserved
keywords. These keywords should be added to the nonReservedKeyword() production:
> Technically, these are supposed to be reserved keywords according to the Standard. However,
we wanted to minimize disruption for users by making these non-reserved keywords--and it seems
we failed to. Our good intentions are recorded in the functional spec attached to DERBY-712.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message