[#DERBY-3304] Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable

Derby

Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable

Created: 08/Jan/08 04:26 PM Updated: 30/Jun/09 03:55 PM

Return to search

Component/s:

JDBC

Affects Version/s:

10.4.1.3

Fix Version/s:

10.3.3.0, 10.4.1.3

Time Tracking:

Not Specified

File Attachments:

	File Name	Date Attached	Attached By	Size
	Main.java	2008-01-08 04:26 PM	Daniel John Debrunner	3 kB

Bug behavior facts:	Regression
Resolution Date:	06/Mar/08 05:18 PM

Description

« Hide

Repro (Main.java) that shows changed behavior after svn 602991
(the patch committed for this issue). It seems a regression: (originally from Dag H. Wanvik attached to ~~DERBY-1585~~)

An explicit commit inside a stored procedure makes a dynamic result sets passed out unavailable, even if the commit is executed *prior* to the result set; as in the repro.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Daniel John Debrunner made changes - 08/Jan/08 04:26 PM

Field	Original Value	New Value
Attachment		Main.java [ 12372721 ]

Mamta A. Satoor made changes - 31/Jan/08 06:47 PM

Assignee

Mamta A. Satoor [ mamtas ]

Mamta A. Satoor made changes - 05/Mar/08 06:31 AM

Fix Version/s		10.4.0.0 [ 12312540 ]
Fix Version/s		10.3.2.2 [ 12312885 ]

Mamta A. Satoor made changes - 06/Mar/08 05:18 PM

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]

Dag H. Wanvik made changes - 30/Jun/09 03:55 PM

Bug behavior facts

[Regression]