On this level, it's more of an apache/web-server-in-general issue.
There are 2 connections to be considered here: the connection between
the browser and the web server and the connection between the
webserver (running PHP for example) and the database and they have
very different behaviours.
If the connection is lost between the web server and the database, the
connection will abort and any pending uncommited operations are rolled
If the connection is lost between the browser and the webserver, that
is another matter. Generally, webservers do not notify server-side
applications of that connection abort so that code will continue to
completion with it's output being lost to the ether. As the
application is not notified of the disconnect; the database server
never hears about it and continues to do as requested.
So: connection lost between browser and webserver affects nothing
except the browser... Should the server-side application itself
abort, uncommited changes will be lost.
On Mon, Apr 19, 2010 at 8:36 AM, Johan De Meersman <vegivamp@stripped> wrote:
> On Fri, Apr 16, 2010 at 1:31 PM, Nigel Wood <nwood@stripped> wrote:
>> P.S. Sorry to the other list users for a PHP oriented discussion.
> Get a room, you two :-)
> Bier met grenadyn
> Is als mosterd by den wyn
> Sy die't drinkt, is eene kwezel
> Hy die't drinkt, is ras een ezel
- michael dykman
May the Source be with you.