[DERBY-1364] Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.2.1, 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: JDBC, Network Client
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 01/Jun/06 17:07
• Updated: 10/Jul/06 14:27
• Resolved: 03/Jul/06 13:13

Description

When executing a stored procedure with executeQuery() and the proc
doesn't return exactly one result set, the query should fail and the
statement should be rolled back. Embedded does this correctly.

The client driver, however, does not roll back the statement, so the
effects of statements executed on nested connections in the stored
procedure are still visible. The reason for this is that the network
server executes the statement with execute() instead of
executeQuery(), so that it succeeds on the server. The client then
counts the number of result sets, and raises an exception if it is not
one, but it does not roll back the effects of the stored procedure.
verified that.)

The same problem exists for executeUpdate(). JCC also has these
problems.