Re: Close SQL Cursor without Ending Module

On Wed, Dec 5, 2012 at 1:41 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Your program can and does tell the DB it's done with a cursor, but it's up
to the DB to close the tables when it feels it's appropriate.

I still don't see why a program shouldn't have the ability to tell the
DB: "Hey, I know you're trying to optimize things for me, but I am
explicitly done with this, and I really want others to be able to use
it (or whatever resources are associated with it) without hassle. If
it turns out I need it again later, I'll ask for it explicitly and
accept the performance penalty."

That 20yr old process that expected all activity to cease at 5pm needs a
little updating. :)

The OP never mentioned anything about a 20-year-old process, that was
all you. And honestly, it's irrelevant. The DB obligingly releases
resources in a reasonable amount of time if the program ends; why
doesn't the DB release resources in a reasonable amount of time from
when the program says it's done with those resources?

John