[DERBY-6729] ResultSet should accept a BigInteger request for a BIGINT column

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.10.2.0, 10.11.1.1
• Component/s: JDBC
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Michael McCarthy
• Created: 06/Sep/14 09:08
• Updated: 01/Feb/17 15:38

Description

I raised an issue on the Spring Framework JIRA at https://jira.spring.io/browse/SPR-12157 for something I thought was Spring related but looks like it may be down to behaviour in Derby.

Not sure if it is a bug as such but in Spring 4.1 they are retrieving items from the resultset in a slightly different way, using getObject(index, requiredType) rather than simply getObject(index). This approach works with H2 and HSQLDB but not with Derby.

There is a pull request with a failing test that describes this on the thread for that ticket. Thanks

Issue Links

• is related to: DERBY-6445 JDBC 4.2: Add support for new date and time classes