At 08:38 PM 14/10/2010, Dimitry Sibiryakov wrote:

>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.

Oh no it doesn't. While I agree the "invalid handle" is obscure, I can't see how "dirty input handle" improves its lucidity in the slightest.

Helen