14.10.2010 9:28, Dmitry Yemanov wrote:

> Even a temporary leak is important. A prepared statement handle may
> block deletion of the affected table or index, an active transaction may
> block garbage collection, attachments may occupy significant amounts of
> memory. Personally, I'd hate to have those "leaks" existing until your
> application decides to terminate.

In this case I would suggest to change error message to something more precise.
"Invalid handle" doesn't make enough information for decision-making. "Dirty input handle"
sounds good enough.

--
SY, SD.