[#DERBY-1314] Differences between client and embedded when invoking stored procedures using Statement.executeUpdate()

Derby

Differences between client and embedded when invoking stored procedures using Statement.executeUpdate()

Created: 10/May/06 08:30 PM Updated: 18/Sep/06 03:26 PM

Return to search

Component/s:

JDBC

Affects Version/s:

10.2.1.6

Fix Version/s:

10.2.1.6

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
derby-1314-v1.diff	2006-06-13 06:38 PM	Knut Anders Hatlen	4 kB
derby-1314-v1.stat	2006-06-13 06:38 PM	Knut Anders Hatlen	0.2 kB

Issue Links:

Reference

This issue is related to:

DERBY-211 Network Server returns no result sets for a procedure call that returns no result

Issue & fix info:	Patch Available, Release Note Needed
Resolution Date:	23/Jun/06 07:23 PM

Description

« Hide

When invoking a stored procedure using Statement.executeUpdate(), the
client driver and the embedded driver behave differently.

If the stored procedure does not return any result set, the embedded
driver returns 0, whereas the client returns -1.

If the stored procedure returns one or more result sets, the embedded
driver returns -1, whereas the client fails with an exception.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Knut Anders Hatlen made changes - 10/May/06 08:35 PM

Field	Original Value	New Value
Link		This issue is related to DERBY-211 [ DERBY-211 ]

Knut Anders Hatlen made changes - 06/Jun/06 04:51 PM

Assignee

Knut Anders Hatlen [ knutanders ]

Knut Anders Hatlen made changes - 13/Jun/06 06:38 PM

Attachment		derby-1314-v1.stat [ 12335378 ]
Attachment		derby-1314-v1.diff [ 12335377 ]

Knut Anders Hatlen made changes - 13/Jun/06 06:50 PM

Derby Info

[Patch Available, Release Note Needed]

Knut Anders Hatlen made changes - 21/Jun/06 08:22 PM

Status

Open [ 1 ]

In Progress [ 3 ]

Knut Anders Hatlen made changes - 23/Jun/06 07:23 PM

Status	In Progress [ 3 ]	Closed [ 6 ]
Resolution		Fixed [ 1 ]
Fix Version/s		10.2.0.0 [ 11187 ]