You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2016/09/26 14:57:20 UTC

[jira] [Comment Edited] (IGNITE-3876) ODBC: Check all output parameters for nulls before assignment.

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

Semen Boikov edited comment on IGNITE-3876 at 9/26/16 2:57 PM:
---------------------------------------------------------------

Fixed


was (Author: vozerov):
Fixed.

> ODBC: Check all output parameters for nulls before assignment. 
> ---------------------------------------------------------------
>
>                 Key: IGNITE-3876
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3876
>             Project: Ignite
>          Issue Type: Task
>          Components: odbc
>    Affects Versions: 1.7
>            Reporter: Igor Sapego
>            Assignee: Vladimir Ozerov
>              Labels: odbc
>             Fix For: 1.8
>
>
> Currently, we suppose that all the output pointer parameters are not null and point to the valid data. Practice shows that a lot of users call ODBC functions with NULL parameters if they don't need some of the output values. Review the API and add all necessary null-checks.



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