[
https://issues.apache.org/jira/browse/IGNITE-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180654#comment-16180654
]
Alexander Paschenko commented on IGNITE-6286:
---------------------------------------------
[~schernolyas]
Hello, my comments:
1. Please remove {{log.info}} statement from {{bindObject}} and from test class
- looks like these are leftovers from debugging stage.
2. Please add javadocs to all test class members.
3. Instead of constructing a {{QueryEntity}} via reflection in test class,
please do following:
3.1. Mark data fields of {{Bookmark}} class with Ignite's
{{@QuerySqlField}} annotation.
3.2. Use method {{CacheConfiguration#setIndexedTypes}} to register indexed
type in Ignite.
4. Please get rid of massive code duplication in test methods. You could simply
move all checks to a single method that would check all fields, that's fine.
> 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)
