[
https://issues.apache.org/jira/browse/IGNITE-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183831#comment-16183831
]
Sergey Chernolyas edited comment on IGNITE-6286 at 9/28/17 8:08 AM:
--------------------------------------------------------------------
Hi [~al.psc]
Your points 2-4 are fixed. Could you please review
https://github.com/apache/ignite/pull/2750.
was (Author: schernolyas):
Hi!
Please review https://github.com/apache/ignite/pull/2750
> org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number of characters
> ------------------------------------------------------------------------------
>
> Key: IGNITE-6286
> URL: https://issues.apache.org/jira/browse/IGNITE-6286
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.1
> Reporter: Sergey Chernolyas
> Assignee: Sergey Chernolyas
> Labels: usability
> Fix For: 2.3
>
>
> Binding values of some types to parameterized queries leads to the exception
> (see fill stacktrace in comments).
> Also, the exception *blocks* using parameterized queries for Hibernate OGM.
> I proceed the exception for String type. For control it, I developed test (
> see
> org.apache.ignite.internal.processors.query.IgniteSqlParameterizedQueryTest)
> .
> The exception reproduced for BigDecimal type in 2.3-snapshot.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
