I'm not sure, but I think if you perform a commit or rollback after
retrieving (e.g., in the retrieveEnd event), the cursor will be closed. You
need to take care to do this when you have other uncommited statements, or
you will corrupt your logical transaction.
We have a guideline that says developers are not allowed to perform any
SQL statements or calls that perform insert, update, or delete statements
except within the logical unit of work (aka the pfc_save sequence). This is
good practice anyway, since it prevents a commit/rollback in one window from
affecting incomplete work in another.
--dang
-----Original Message-----
From: Vinod Adimulam [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 24, 2000 08:58
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: PFCSIG Reference cursor
Hi,
I am using PB6.5 (PFC) / Oracle 8 /win 95. I have datawindows based on
stored procedure. The stored procedure uses reference cursors to return
data.The problem is these reference cursors are open in database even after
retrieving and my DBA is after us to close these cursors. The question is
how can I close these cursors? Is there any oracle function or variable by
which I can distroy/close these cursors?
Thanks
Vinod.
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
