Bug #73029 | ResultSetMetaData | ||
---|---|---|---|
Submitted: | 17 Jun 2014 20:14 | Modified: | 17 Jul 2014 21:08 |
Reporter: | root borntobe | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 5.1.31 | OS: | Linux (Debian) |
Assigned to: | CPU Architecture: | Any | |
Tags: | ResultSetMetaData |
[17 Jun 2014 20:14]
root borntobe
[17 Jun 2014 20:19]
root borntobe
We go back to vers. 5.0.4. There it is working.
[17 Jun 2014 21:08]
Mark Matthews
This is more than likely due to JDBC specification clarifications that came along during the 5.1 timeframe. You don't state what actual methods you're calling, so I can only guess. You may want to try adding "useColumnNamesInFindColumn=true" to your JDBC URL, but really it's poor practice to have ambiguous column names in your result sets, it would be better to fix that. If "useColumnNamesInFindColumn" doesn't fix things for you, please show us an example of what methods you are calling that aren't working like you expect.
[18 Jul 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".