Subject | Re: [firebird-support] stale statements in MON$STATEMENTS |
---|---|
Author | Hamish Moffatt |
Post date | 2016-12-02T12:09:50Z |
On 02/12/16 20:59, Dimitry Sibiryakov sd@...
[firebird-support] wrote:
driver, so this should all be managed for me. It should free the
statements when they go out of scope.
It's a bit suspicious that 100 of these statements were the same one,
"merge into...", so I'll have to follow that up.
I also see a ton of connections on MON$ATTACHMENTS from the same thread
in my application (MON$REMOTE_PID, MON$REMOTE_ADDRESS both the same)
which also makes no sense.
Hamish
[firebird-support] wrote:
> 02.12.2016 8:56, Hamish Moffatt hamish@... [firebird-support] wrote:OK, thanks. I'm doing all my Firebird interaction with Qt and its IBASE
>> I understand that the idle statement
>> means they have been prepared but not executed, but this shouldn't be
>> possible in my application source (prepare has never failed, and I
>> always execute).
> Yes, but after execution they are idle again until unprepared or freed.
>
>
driver, so this should all be managed for me. It should free the
statements when they go out of scope.
It's a bit suspicious that 100 of these statements were the same one,
"merge into...", so I'll have to follow that up.
I also see a ton of connections on MON$ATTACHMENTS from the same thread
in my application (MON$REMOTE_PID, MON$REMOTE_ADDRESS both the same)
which also makes no sense.
Hamish