db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-468) Unreserve COUNT keyword, if possible.
Date Fri, 02 Sep 2005 18:25:12 GMT
    [ http://issues.apache.org/jira/browse/DERBY-468?page=comments#action_12320922 ] 

Satheesh Bandaram commented on DERBY-468:

Fix submitted to trunk. Also merged the fix to 10.1 branch.

Sending        java\engine\org\apache\derby\impl\sql\compile\sqlgrammar.jj
Sending        java\testing\org\apache\derbyTesting\functionTests\master\nonreserved.out
Sending        java\testing\org\apache\derbyTesting\functionTests\tests\lang\nonreserved.sql
Transmitting file data ...
Committed revision 267247.

> Unreserve COUNT keyword, if possible.
> -------------------------------------
>          Key: DERBY-468
>          URL: http://issues.apache.org/jira/browse/DERBY-468
>      Project: Derby
>         Type: Improvement
>   Components: SQL
>     Versions:,,
>  Environment: All Platforms
>     Reporter: Satheesh Bandaram
>     Priority: Minor
>  Attachments: count.patch
> Derby currently treats COUNT as a reserved word. This prevents having COUNT as a table
name or a column name as shown below. It would be good to move COUNT from reserved word to
a non-reserved word list. Having COUNT as a reserved word also causes problems while porting
applications to Derby.
> ij> create table count(i int);
> ERROR 42X01: Syntax error: Encountered "count" at line 1, column 14.
> ij> create table ts(count int);
> ERROR 42X01: Syntax error: Encountered "count" at line 1, column 17.
> Note that SQL standard says COUNT is a reserved word, but Derby treats several of these
reserved words as non-reserved words already. (CLOB for example)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message