[DERBY-5254] The keywords introduced by the CREATE SEQUENCE work are treated as reserved rather than unreserved.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2
• Fix Version/s: 10.6.2.4, 10.7.1.4, 10.8.2.2, 10.9.1.0
• Component/s: SQL
• Urgency: Normal
• Issue & fix info: Known fix
• Bug behavior facts: Regression, Seen in production
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 31/May/11 16:04
• Updated: 14/Jun/13 17:25
• Resolved: 01/Jun/11 13:09

Description

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.

Issue Links

• is related to: DERBY-712 Support for sequences