| Subject | Re: [firebird-support] queries running after disconnect |
|---|---|
| Author | unordained |
| Post date | 2004-02-03T02:27:22Z |
I rather figured that if the server were to be smart enough to cancel a query because nobody's
listening, it would also cancel the send-buffer for that connection. Unless you just meant that the
server would continue sending data to a client that requested the data (and hasn't disconnected)
even if the query was cancelled explicitely (on a different connection, even)? That's separate from
clearing the send-buffer if the client disconnects, yes. If the query's not done pulling, I'd
expect the server to send an error to the client, rather than more data. If the data's all ready,
and the client's listening ... that'd be cause for a different command to cancel -that-, and send
an unexpected-end-of-data error. I'm not particularly interested in that -- my problems usually
deal with queries that return exactly what I want, but take a while.
Since Alexander says 2.0 should have dropped-connection-checking, I guess I'll be looking forward
to it along with everyone else.
G'day Helen,
-Philip
---------- Original Message -----------
From: Helen Borrie <helebor@...>
To: firebird-support@yahoogroups.com
Sent: Tue, 03 Feb 2004 10:19:01 +1100
Subject: Re: [firebird-support] queries running after disconnect
listening, it would also cancel the send-buffer for that connection. Unless you just meant that the
server would continue sending data to a client that requested the data (and hasn't disconnected)
even if the query was cancelled explicitely (on a different connection, even)? That's separate from
clearing the send-buffer if the client disconnects, yes. If the query's not done pulling, I'd
expect the server to send an error to the client, rather than more data. If the data's all ready,
and the client's listening ... that'd be cause for a different command to cancel -that-, and send
an unexpected-end-of-data error. I'm not particularly interested in that -- my problems usually
deal with queries that return exactly what I want, but take a while.
Since Alexander says 2.0 should have dropped-connection-checking, I guess I'll be looking forward
to it along with everyone else.
G'day Helen,
-Philip
---------- Original Message -----------
From: Helen Borrie <helebor@...>
To: firebird-support@yahoogroups.com
Sent: Tue, 03 Feb 2004 10:19:01 +1100
Subject: Re: [firebird-support] queries running after disconnect
> At 07:43 PM 2/02/2004 +0100, you wrote:------- End of Original Message -------
> > I remember that firebird polls
> >each connection every few (180?) seconds to make sure the client is still
> >there
>
> Yep, but only an inactive connection. From the POV of the server, if it is
> still running a query for a connection or has unfetched rows waiting for
> the connection, the connection is still there.
>
> So, even when we get the ability to stop a runaway query, you will still
> have your problem if you are writing applications that return a gazillion
> records in bufferloads of 18 for your beloved DBGrid interface.
>
> That is why, on the eighth day, God created the WHERE clause.
>
> /heLen
>
>
> Yahoo! Groups Links
>
> To visit your group on the web, go to:
> http://groups.yahoo.com/group/firebird-support/
>
> To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
>
> Your use of Yahoo! Groups is subject to:
> http://docs.yahoo.com/info/terms/