pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rick Morris <rick@brainscraps.com>
To: Chris <dmagick@gmail.com>
Cc: Herbie McDuck <herbie@faams.net>
Cc: Alan Hodgson <ahodgson@simkin.ca>
Cc: pgsql-php@postgresql.org
Subject: Re: PostgreSQL locking from PHP scripts
Date: Tue, 07 Nov 2006 02:52:40 -0500
Message-ID: <45503B48.6020803@brainscraps.com> (raw)
In-Reply-To: <454FE031.2080004@gmail.com>
References: <20061026181147.50048.qmail@web51309.mail.yahoo.com>
	<200611061105.29055@hal.medialogik.com>
	<454FD71E.6070807@faams.net>
	<454FE031.2080004@gmail.com>

Chris wrote:
> Herbie McDuck wrote:
>> Alan Hodgson wrote:
>>> On Thursday 26 October 2006 11:11, Amal burman 
>>> <amalburman@yahoo.com> wrote:
>>>  
>>>> postgresql database for this project. Here script one
>>>> (booking.php) tries to setup a lock for update and ask
>>>> user to fill-up the form. Now when the user fill-up
>>>> the form and submit it for update, second script
>>>> (update.php) update the database and releasing the
>>>> locks.     
>>>
>>> You can't do this kind of thing in PHP.  PHP resets the database 
>>> connection between scripts.   The script is finished as soon as the 
>>> page is delivered to the client.
>>>
>>> Also, web connections are stateless and there is no way to even know 
>>> what web server process or database connection you'll be getting on 
>>> subsequent page views.   
>> So is PHP and 'ANY' database a useless adventure when it goes to 
>> developing a robust business and accounting package?
>
> No, it applies to anything you do in a web browser.
>
> The HTTP protocol is "stateless" which means all resources, 
> connections etc are killed at the end of the script. Resources of any 
> type are not kept alive at the end of a script.
>
> It's not a php thing or <insert random language here>, it's a HTTP 
> protocol thing.
>
There is another way to approach this with PHP and other random 
languages, as long as scripts can be executed outside of the context of 
an HTTP server module (such as PHP in CLI mode): have a the web script 
interact with a standalone commandline script or daemon that lives 
across requests. Thus your HTTP-requested PHP script could communicate 
via some IPC method to a PHP-CLI script which holds the database 
connections, binds them to a session ID and actually handles the 
mechanics of transactions and queries (a simple connection pooling 
method, if you will) and thus transactions can be maintained across 
multiple requests.

Now, saying it and doing it are two different things, I understand; not 
exactly trivial to implement. But still, if it is important enough to 
your application, it can be done. And, I have found PHP to be quite 
stable running in daemon mode. At least, amply stable enough to handle 
transactions that span minutes or hours. (I have had PHP daemon scripts 
run for weeks without problem)





view thread (12+ messages)  latest in thread

Message-ID: <45503B48.6020803@brainscraps.com>
Permalink:  ../45503B48.6020803@brainscraps.com/
Also on:    postgresql.org/message-id/45503B48.6020803@brainscraps.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: rick@brainscraps.com, dmagick@gmail.com, herbie@faams.net, ahodgson@simkin.ca
  Subject: Re: PostgreSQL locking from PHP scripts
  In-Reply-To: <45503B48.6020803@brainscraps.com>
  References: <20061026181147.50048.qmail@web51309.mail.yahoo.com> <200611061105.29055@hal.medialogik.com> <454FD71E.6070807@faams.net> <454FE031.2080004@gmail.com> <45503B48.6020803@brainscraps.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox