[
https://issues.apache.org/jira/browse/DERBY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539417
]
Myrna van Lunteren commented on DERBY-2245:
-------------------------------------------
After lack of response on the list (except from Dan, thx) and some more thought:
- there is no mention of 'reserved' in the javadoc, and it's not clear what the
behavior is supposed to be if you use a reserved keyword. So it's hard to
verify what are
really the reserved keywords. So we'll just take the current split between
reserved and non-reserved in sqlgrammar.jj as truth.
- Wikipedia says: 'A keyword is a word or concept with special significance'
and 'an identifier in a computer language that indicates a specific command '.
So again, this suggests all keywords, not just reserved.
- the spirit of the call is to return non-sql keywords, not specific to which
SQL spec. So, let's not make a difference between jdk16 and jdk14/15 (jdk16
says non-SQL2003, earlier says non-SQL92).
So, I propose to:
- move the XML related (and any other non SQL99, but SQL2003 - which would
they be?) keywords into the SQL reserved keywords area
- modify the javadoc to say, SQL2003, rather than SQL92.
- update any relevant docs
- make getSQLKeywords return all non SQL keywords (i.e. both those in the
reserved, and non-reserved area).
> DatabaseMetaData.getSQLKeywords() contains words that are not keywords in
> Derby.
> --------------------------------------------------------------------------------
>
> Key: DERBY-2245
> URL: https://issues.apache.org/jira/browse/DERBY-2245
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6, 10.2.2.0
> Reporter: Daniel John Debrunner
> Assignee: Saurabh Vyas
> Priority: Minor
>
> Such as REFRESH and PUBLICATION.
> Not sure what the exact contents should be.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
