[ https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798966#comment-16798966 ]
Dmitry Melnichuk commented on IGNITE-11593: ------------------------------------------- Today I did a little research on this topic. Seems like Ignite SQL accepts VARBINARY data as an UTF8/ASCII string, that consists of hexadecimal digit pairs, but returns it as an array of integers, with each integer representing a byte value. For example, this code behaves quite as expected: {code} client.sql('DROP TABLE test_sql_binary IF EXISTS') client.sql( 'CREATE TABLE test_sql_binary(id int primary key, varbin VARBINARY)' ) client.sql( 'INSERT INTO test_sql_binary(id, varbin) VALUES (?, ?)', query_args=(1, '0123456789abcdef'), ) result = client.sql('SELECT * FROM test_sql_binary') data = list(*result)[1] print(data) # [1, 35, 69, 103, -119, -85, -51, -17] {code} I do not know why Ignite accepts your arguments on server side without throwing an SQL error. As for client side, I think this is not a bug. > python thin client: insert and select VARBINARY data type through SQL > --------------------------------------------------------------------- > > Key: IGNITE-11593 > URL: https://issues.apache.org/jira/browse/IGNITE-11593 > Project: Ignite > Issue Type: Bug > Components: thin client > Affects Versions: 2.7 > Reporter: Stepan Pilschikov > Assignee: Dmitry Melnichuk > Priority: Major > > varbin data type select is getting not parsed array of integer values > Example: > https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)