You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/06/19 17:47:00 UTC
[jira] [Assigned] (IMPALA-1758) Impala ODBC Driver returns
incorrect SQLState for "Table does not exist"
[ https://issues.apache.org/jira/browse/IMPALA-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong reassigned IMPALA-1758:
-------------------------------------
Assignee: (was: Justin Erickson)
> Impala ODBC Driver returns incorrect SQLState for "Table does not exist"
> ------------------------------------------------------------------------
>
> Key: IMPALA-1758
> URL: https://issues.apache.org/jira/browse/IMPALA-1758
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
> Affects Versions: Impala 2.1.1
> Reporter: Viji
> Priority: Minor
> Labels: jdbc, odbc, sql-language, usability
>
> ODBC specification states that an ODBC driver should return SQLState 42S02 for a "Table does not exist" condition, but the Impala ODBC driver (version 2.5.23 on Windows 7) is currently returning HY000 instead. Applications check for specific SQLStates to make better code choices and rely on those SQLStates to be accurate. The HY000 SQLState only indicates "General error".
> This can be reproduced with any ODBC application that displays detailed error messages by simply executing:
> SELECT * FROM tablethatdoesnotexist
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org