Re: PostgreSQL locking from PHP scripts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Herbie McDuck wrote:
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?

Not at all. It just means that you'll have to create your own "state" logic using sessions. For instance, create a column within the necessary table that you can check to see whether or not some other process/user is using the record in question and then build the necessary logic around that to enable/disable access to the records.

This is something that isn't specific to PHP. You'll encounter the same issues with any other middleware language that uses a web browser as it's primary means of interaction. HTTP just doesn't keep track of the state of your application. It's up to you as the developer to handle that.

Charley


[Index of Archives]     [Postgresql General]     [Postgresql Admin]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Yosemite Backpacking]     [Postgresql Jobs]

  Powered by Linux