You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2011/05/31 18:06:48 UTC
[jira] [Created] (DERBY-5254) The keywords introduced by the CREATE
SEQUENCE work are treated as reserved rather than unreserved.
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.8.1.2, 10.7.1.1, 10.6.2.1, 10.6.1.0
Reporter: Rick Hillegas
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
[jira] [Updated] (DERBY-5254) The keywords introduced by the CREATE
SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5254:
----------------------------------
Bug behavior facts: [Regression, Seen in production] (was: [Seen in production])
> 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
>
> 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
[jira] [Updated] (DERBY-5254) The keywords introduced by the CREATE
SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ 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 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
[jira] [Commented] (DERBY-5254) The keywords introduced by the
CREATE SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042152#comment-13042152 ]
Rick Hillegas commented on DERBY-5254:
--------------------------------------
Ported 1130127 from trunk to 10.6 branch at subversion revision 1130139.
> 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
[jira] [Commented] (DERBY-5254) The keywords introduced by the
CREATE SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Assigned] (DERBY-5254) The keywords introduced by the
CREATE SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reassigned DERBY-5254:
------------------------------------
Assignee: Rick Hillegas
> 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
>
> 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
[jira] [Commented] (DERBY-5254) The keywords introduced by the
CREATE SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042141#comment-13042141 ]
Rick Hillegas commented on DERBY-5254:
--------------------------------------
Ported 1130127 from trunk to 10.8 branch at subversion revision 1130130.
> 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
[jira] [Commented] (DERBY-5254) The keywords introduced by the
CREATE SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042133#comment-13042133 ]
Rick Hillegas commented on DERBY-5254:
--------------------------------------
Regression tests passed cleanly for me. Committed derby-5254-01-aa-unreserveKeywords.diff to trunk at subversion revision 1130127.
> 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
[jira] [Resolved] (DERBY-5254) The keywords introduced by the
CREATE SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas resolved DERBY-5254.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
10.8.1.3
10.7.1.4
10.6.2.3
Issue & fix info: [Known fix] (was: [Patch Available, Known fix])
> 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
> Fix For: 10.6.2.3, 10.7.1.4, 10.8.1.3, 10.9.0.0
>
> 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
[jira] [Updated] (DERBY-5254) The keywords introduced by the CREATE
SEQUENCE work are treated as reserved rather than unreserved.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-5254:
---------------------------------
Issue & fix info: [Known fix, Patch Available] (was: [Known fix])
> 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