You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2005/09/13 20:23:54 UTC
[jira] Created: (DERBY-565) Misleading parser diagnostics
Misleading parser diagnostics
-----------------------------
Key: DERBY-565
URL: http://issues.apache.org/jira/browse/DERBY-565
Project: Derby
Type: Bug
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-565) Misleading parser diagnostics
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ 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: 10.1.1.0
> 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.
[jira] Updated: (DERBY-565) Misleading parser diagnostics
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-565?page=all ]
Rick Hillegas updated DERBY-565:
--------------------------------
Version: 10.1.1.0
Update "affects version" field.
> Misleading parser diagnostics
> -----------------------------
>
> Key: DERBY-565
> URL: http://issues.apache.org/jira/browse/DERBY-565
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.1.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-565) Misleading parser diagnostics
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-565?page=all ]
Mike Matrigali updated DERBY-565:
---------------------------------
Component: SQL
> Misleading parser diagnostics
> -----------------------------
>
> Key: DERBY-565
> URL: http://issues.apache.org/jira/browse/DERBY-565
> Project: Derby
> Type: Bug
> Components: SQL
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira