[
https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042148#comment-13042148
]
Rick Hillegas commented on DERBY-5254:
--------------------------------------
Ported 1130127 from trunk to 10.7 branch at subversion revision 1130133.
> The keywords introduced by the CREATE SEQUENCE work are treated as reserved
> rather than unreserved.
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-5254
> URL: https://issues.apache.org/jira/browse/DERBY-5254
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2
> 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:
> MAXVALUE
> MINVALUE
> CYCLE
> 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
