|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I would like to second Richard Kennard's statement. This is an egregious error in the exact scenario he mentions.
The performDiscovery eventually maps down to resultSetMetaData.getColumnName( position ). Switching it to resultSetMetaData.getColumnLabel( position ) should fix the bug.
Why do the specific type classes (AbstractBinaryType) retrieve data by name in the first place? Shouldn't they be positional as well? Seems like relying on something to be unique that isn't ever specified to be unique is just asking for trouble.
Looks like a simple fix for a pretty big correctness issue. Thoughts?