db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-565) Misleading parser diagnostics
Date Fri, 10 Jul 2009 21:35:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali updated DERBY-565:

    Urgency: Normal

Triaged July 10, 2009: assigned normal urgency. 

> Misleading parser diagnostics
> -----------------------------
>                 Key: DERBY-565
>                 URL: https://issues.apache.org/jira/browse/DERBY-565
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Priority: Minor
> Bryan Pendleton reports:
> When I mistype 'join' as 'joing', the error message that I
> get actually complains about the word 'left'. It ought to,
> in my opinion, complain about the word 'joing', since that
> is truly the word with the syntax error in it.
> ij> select * from t1 left outer joing t2 on t1.c2=t2.c1;
> ERROR 42X01: Syntax error: Encountered "left" at line 1, column 18.
> I don't know if this is a PITA to fix or not, but I thought
> I'd send it along anyway since it was so easy to reproduce. 
> -------------------------------------------------------
> This appears to be a problem with hand-coded lookahead logic. Although fixing this particular
lookahead issue might be trivial, this is part of a larger problem since the parser is liberally
peppered with similar hand-coded lookahead logic. Coming up with a general solution might
involve some creativity.

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

View raw message