[ 
https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559880#action_12559880
 ] 

Kristian Waagan commented on DERBY-2103:
----------------------------------------

The javacc-152 issue has been fixed, and is marked for inclusion in the 4.1 
milestone.
I do not know the planned release date, but we should keep our eyes open and 
consider upgrading JavaCC when the update is out.

> After a Lexical Error due to syntax error ,    even a simple create table 
> does not work  on the same connection.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2103
>                 URL: https://issues.apache.org/jira/browse/DERBY-2103
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.1.4
>            Reporter: Suresh Thalamati
>            Assignee: Mayuresh Nirhali
>            Priority: Minor
>             Fix For: 10.2.3.0, 10.3.1.4
>
>         Attachments: derby2103.diff, derby2103_v2.diff, Derby2103_v3.diff
>
>
> connect 'jdbc:derby:wombat;create=true';
> create table t1(a int ) ;
> create table "t2"(a int ) ;
> -- this should fail. 
> create table foo (a int ,  \"YEAR\" int ) ;
> -- but this should not fail. But failing
> create table t4 ( b int ) ;
> FYI:
> $ java org.apache.derby.tools.ij
> ij version 10.3
> ij> run 'weird1.sql';
> ij> connect 'jdbc:derby:wombat;create=true';
> ij> create table t1(a int ) ;
> 0 rows inserted/updated/deleted
> ij> create table "t2"(a int ) ;
> 0 rows inserted/updated/deleted
> ij> -- this should fail.
> create table foo (a int ,  \"YEAR\" int ) ;
> ERROR 42X02: Lexical error at line 2, column 28.  Encountered: "\\" (92), 
> after
> : "".
> ij> -- but this should not fail. But failing
> create table t4 ( b int ) ;
> ERROR 42X01: Syntax error: Encountered "" at line 2, column 21.
> ij>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to