Bug #4723 ResultSet.getLong does not set wasNullFlag properly
Submitted: 23 Jul 2004 15:04 Modified: 27 Jul 2004 0:55
Reporter: Dmitriy Degtiarev Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / J Severity:S2 (Serious)
Version:3.1-nightly-20040722 OS:Windows (WinXP)
Assigned to: Assigned Account CPU Architecture:Any

[23 Jul 2004 15:04] Dmitriy Degtiarev
Description:
If wasNullFlag is set to true, calls to getLong return a value, but wasNullFlag remains true. 

This is serious bug, because at least Hibernate doesn't work with these 3.1 drivers.

How to repeat:
the ResultSet should be binary encoded

1. retrieve any null value from ResultSet
2. call getLong on any non-null value
3. check wasNull()

Suggested fix:
add line 

wasNullFlag = false;

to the beginning of every getLong, getInt, etc. method
[27 Jul 2004 0:55] Dean Ellis
Duplicate of 4689; has been corrected in current development sources.