Re: Lifetime of statement-based storage engine resources

[Sergei Golubchik]

Hi!

On May 09, Timothy P Clark wrote:
> 
> As it is, I'm having to scatter code to clean up resources across
> several of these functions. Then it's a process of trial and error
> while I figure out what is being freed too early and what is leaking.
> What I need is a single handler method that MySQL calls to say, "This
> statement is done; results have been sent to the user; whatever
> resources you needed internally to accomplish this operation may now
> be freed." Am I missing something that already exists? Is there a
> reliable way to do this with the current design?

It's external_lock() at the moment (called with lock_type=F_UNLCK).

Regards / Mit vielen Grüssen,
Sergei

-- 
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <serg@stripped>
 / /|_/ / // /\ \/ /_/ / /__  Principal Software Engineer/Server Architect
/_/  /_/\_, /___/\___\_\___/  Sun Microsystems GmbH, HRB München 161028
       <___/                  Sonnenallee 1, 85551 Kirchheim-Heimstetten
Geschäftsführer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Häring