Re: Null column values - bug

2016-11-09 Thread Anil
f differences manually. > > For example: > Ignite ver. 1.7.0#20160801-sha1:383273e3f66f702de2482466dce954d570a8ccf2 > > This is identifier of commit 383273e3f66f702de2482466dce954d570a8ccf2 > > > > -- > View this message in context: http://apache-ignite-users. >

Re: Null column values - bug

2016-11-09 Thread vdpyatkov
383273e3f66f702de2482466dce954d570a8ccf2 -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Null-column-values-bug-tp8692p8826.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Null column values - bug

2016-11-04 Thread Anil
Are there any differences between iginite 1.7.0-SNAPSHOT and 1.7 ? please clarify. Thanks.

Re: Null column values - bug

2016-11-03 Thread Andrey Mashenkov
Yes, you are right. This is a bug. It seems there should be smth like this: wasNull == curr.get(colIdx - 1) == null; I've create an issue https://issues.apache.org/jira/browse/IGNITE-4175 Thanks Anil ! On Thu, Nov 3, 2016 at 9:45 PM, Anil wrote: > following code i see in

Re: Null column values - bug

2016-11-03 Thread Anil
following code i see in the JdbcResultSet. val is not null for null values for string types. then val == null is false. correct ? T val = cls == String.class ? (T)String.valueOf(curr.get(colIdx - 1)) : (T)curr.get(colIdx - 1); wasNull = val == null; On 3 November 2016 at 23:48, Andrey

Re: Null column values - bug

2016-11-03 Thread Andrey Mashenkov
No, wasNull is true if column value is null otherwise false. You can have wasNull() is true but getInt() is zero. E.g. getInt() return type is primitive and default value (zero) shoud be return for NULL fields. On Thu, Nov 3, 2016 at 9:11 PM, Anil wrote: > wasNull is false

Re: Null column values - bug

2016-11-03 Thread Anil
wasNull is false all the time for string types. correct ? On 3 November 2016 at 20:39, Andrey Mashenkov wrote: > Javadoc says that null value should be returned. > > But from the other side, there is wasNull() method, that should be use for > null checks. > > > > On

Re: Null column values - bug

2016-11-03 Thread Andrey Mashenkov
Javadoc says that null value should be returned. But from the other side, there is wasNull() method, that should be use for null checks. On Thu, Nov 3, 2016 at 5:39 PM, Andrey Gura wrote: > String.valuOf(null) return "null" string by contract. > > On Thu, Nov 3, 2016 at

Null column values - bug

2016-11-03 Thread Anil
HI , null values are returned as "null" with ignite jdbc result set. private T getTypedValue(int colIdx, Class cls) throws SQLException { ensureNotClosed(); ensureHasCurrentRow(); try { T val = cls == String.class ? (T)String.valueOf(curr.get(colIdx - 1)) :

Re: Null column values - bug

2016-11-03 Thread Andrey Gura
String.valuOf(null) return "null" string by contract. On Thu, Nov 3, 2016 at 5:33 PM, Anil wrote: > HI , > > null values are returned as "null" with ignite jdbc result set. > > private T getTypedValue(int colIdx, Class cls) throws SQLException > { >