From: | Herbie McDuck <herbie(at)faams(dot)net> |
---|---|
To: | Alan Hodgson <ahodgson(at)simkin(dot)ca> |
Cc: | pgsql-php(at)postgresql(dot)org |
Subject: | Re: PostgreSQL locking from PHP scripts |
Date: | 2006-11-07 00:45:18 |
Message-ID: | 454FD71E.6070807@faams.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
Alan Hodgson wrote:
> On Thursday 26 October 2006 11:11, Amal burman <amalburman(at)yahoo(dot)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?
--Hal.
From | Date | Subject | |
---|---|---|---|
Next Message | Chris | 2006-11-07 01:24:01 | Re: PostgreSQL locking from PHP scripts |
Previous Message | Alan Hodgson | 2006-11-06 19:42:17 | Re: PostgreSQL locking from PHP scripts |