[
https://issues.apache.org/jira/browse/IGNITE-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745271#comment-15745271
]
Igor Sapego commented on IGNITE-4421:
-------------------------------------
I found a root cause of the issue. In {{OdbcRequestHandler}} we now acquire
keep-binary cache instance ({{withKeepBinary()}}), so any complex object
returned as an instance of {{BinaryObjectExImpl}}, which serialized as
{{IGNITE_TYPE_BINARY}}. Currently, we don't handle objects of type
{{IGNITE_TYPE_BINARY}} in ODBC driver.
I'm going to implement it.
> ODBC: SQLFetch fails if result set contains non-primitive column.
> -----------------------------------------------------------------
>
> Key: IGNITE-4421
> URL: https://issues.apache.org/jira/browse/IGNITE-4421
> Project: Ignite
> Issue Type: Bug
> Components: odbc
> Affects Versions: 1.8
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Labels: odbc
> Fix For: 2.0
>
>
> If any column of the result set is complex binary object (non primitive
> type), then {{SQLFetch}} fails upon call with the following message:
> {noformat}
> Error 01S01: Can not retrieve row column.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
