You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/30 13:14:58 UTC

[jira] [Commented] (IGNITE-4493) ODBC: Add missing diagnostic records in case of API errors

    [ https://issues.apache.org/jira/browse/IGNITE-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787650#comment-15787650 ] 

ASF GitHub Bot commented on IGNITE-4493:
----------------------------------------

GitHub user skalashnikov opened a pull request:

    https://github.com/apache/ignite/pull/1396

    IGNITE-4493: ODBC: Added missing diagnostic records for error cases

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-4493

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1396.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1396
    
----
commit b3535988164bebba6810bce3ed4d2564af88df5f
Author: skalashnikov <sk...@gridgain.com>
Date:   2016-12-30T13:11:28Z

    IGNITE-4493: Added missing diagnostic record for errors

commit 751428212cf9a9f61010b297b0d7d6e0fbe4d764
Author: skalashnikov <sk...@gridgain.com>
Date:   2016-12-30T13:12:54Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-4493

----


> ODBC: Add missing diagnostic records in case of API errors
> ----------------------------------------------------------
>
>                 Key: IGNITE-4493
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4493
>             Project: Ignite
>          Issue Type: Bug
>          Components: odbc
>    Affects Versions: 1.8
>            Reporter: Sergey Kalashnikov
>            Assignee: Sergey Kalashnikov
>             Fix For: 2.0
>
>
> The following functions in Ignite ODBC driver do not strictly follow the API documentation with regard to diagnostics. It should be possible to obtain additional information about errors via SQLGetDiagRec() call.
> SQLAllocHandle
> SQLFreeHandle
> SQLFreeStmt
> SQLBindCol
> SQLFetchScroll
> SQLBindParameter



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)