[DERBY-1288] Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.2.1.6
• Component/s: JDBC
• Assignee: Knut Anders Hatlen
• Reporter: Richard N. Hillegas
• Created: 04/May/06 23:24
• Updated: 10/May/06 18:58
• Resolved: 10/May/06 16:42

Description

The following statement raises an error in Derby:

statement.executeQuery( "

{call foo()}" );

although this statement works:

statement.executeUpdate( "{call foo()}

" );

According to section 6.4 of the latest draft of the JDBC4 Compliance chapter, both statements are supposed to work in order to claim Java EE JDBC Compliance.

We need to bring Derby into compliance by supporting executeQuery() on escaped procedure invocations.

Issue Links

• is a clone of: DERBY-501 Client and embedded drivers differ on invoking a procedure that returns a single Dynamic resultSet using CallableStatement.executeQuery()
• is part of: DERBY-1281 JDBC4 Compliance
• is related to: DERBY-1283 Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()