[
https://issues.apache.org/jira/browse/IGNITE-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180733#comment-16180733
]
Sergey Chernolyas commented on IGNITE-6286:
-------------------------------------------
Hi [~al.psc]
I recreated my PR. Please see https://github.com/apache/ignite/pull/2750 .
I fixed your comments N 1, 2 and 4 (If I understood you correctly).
About comment N3.
The test do same that do Hibernate OGM for Ignite. I mean that JPA Entity not
uses annotation '@QuerySqlField' . Can I remain as is?
> 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)
