db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2245) DatabaseMetaData.getSQLKeywords() contains words that are not keywords in Derby.
Date Wed, 24 Oct 2007 23:57:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537460

Myrna van Lunteren commented on DERBY-2245:

Is this issue stalled? Revision 504234 only removed REFRESH and PUBLICATION.

I had a quick look, and it seems to me that the reason why a user would possibly want to return
this is if it's assumed these keywords have a special effect, i.e. are reserved keywords.

Maybe someone can check on the JDBC spec and say whether this is true, but even if it is not
explicit about this, I would suggest we return the list of reserved non-SQL 92 keywords.

we make this method return the contents of the sqlgrammar.jj section titled '/* Additional
JSQL reserved keywords -- non-SQL92 reserved Keywords */'

However, I - possibly erroneously - assumed that reserved meant that you'd get a syntax error
if you tried to use them in a create table statement; but this is not the case, for instance,
I can create a table with the name 'curdate' for instance. So, are the items listed here 'really'
reserved (non-sql 92) keywords? How can I find out?

Assuming the ones on this list really are reserved keywords, I'd suggest toreturn:

> 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:,,,,,,
>            Reporter: Daniel John Debrunner
>            Assignee: Saurabh Vyas
>            Priority: Minor
> 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.

View raw message