André,
thanks for your answer, which confirms my observation on this: Do you
have documents that will explain this behaviour in detail?
Greetings,
Erik
If a http-connection drops (for any reason), while a huge amount of
data is loaded from the database to the webserver, will Apache::DBI
cancel the loading (means cancel the query) or will it continue
loading the data till the end (means finish the execution of the query
/ not in a transaction) and then become ready for a new request again?
Generally speaking, a response handler responding to a client HTTP
request, will not even know that the client<->httpd connection has been
dropped, before it tries to send something back to the client. Then it
will get a "write to client socket error". But before that, it will not
know.
So, if the response handler (which runs your script/program which runs
the DBI code) is busy doing something with the database server, but not
writing anything back to the client, it will happily continue doing that
for as long as it takes.
When it is done talking to the database server, and starts sending the
data to the client, then it will get the error and probably crash,
unless it is prepared for such errors and returns nicely.
