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 "Robert Gasch (JIRA)" <ji...@apache.org> on 2013/06/28 15:35:19 UTC

[jira] [Created] (DERBY-6282) Provide better error messages on syntax and sql compliance errors

Robert Gasch created DERBY-6282:
-----------------------------------

             Summary: Provide better error messages on syntax and sql compliance errors
                 Key: DERBY-6282
                 URL: https://issues.apache.org/jira/browse/DERBY-6282
             Project: Derby
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 10.9.1.0
         Environment: N/A
            Reporter: Robert Gasch


Currently, when you supply a SQL statement which either has a syntax error or fails for some SQL engine compliance issues (for example: Columns of type 'CLOB' may not be used in CREATE INDEX, ORDER BY, GROUP BY, UNION, INTERSECT, EXCEPT or DISTINCT statements because comparisons are not supported for that type) the system only tells you that this error was encountered. It would be extremely helpful if the information provided would include a SQL command snipped (or alternatively a line & column number) where the error was encountered.

MySql does this and it does make finding errors in complex SQL statements much easier. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira