Hi,
Want to add some notes. Did some further reading on the issue. If a jdbc
callable statement is started on a jdbc connection object.
Say: cs = Conn.prepareCall()
Then it must be put into a begin / end block and under ensure part do
"cs.close"
Begin
cs = Conn.prepareCall("some procedure");
On Sun, Jan 30, 2022 at 1:47 AM Dylan Camilleri wrote:
> Hi,
>
> Want to add some notes. Did some further reading on the issue. If a jdbc
> callable statement is started on a jdbc connection object.
>
> Say: cs = Conn.prepareCall()
>
> Then it must be put into a begin / end block and under
Hi Jeremy,
Yes, I had an issue that I could not use sequel API to get return value
from an oracle procedure. So resorted to going manual by using a jdbc
connection object directly.
After adding the explicit close for the preparecall, have no issues with
leaking db resources. Was my bad for not
