Hello

I explain my situation:
I created a db in which I enter reservations to the hotels, especially
in this entry I have carried out over two web pages (and a.php b.php)
and, since the procedure of inserting a new book contains a number of
steps to perform, I have implemented this procedure through the
commit / rollback and with table locks...

I tested everything with the sleep (PHP).
If I do the test between two pages A and B. .. everything works! The
second page is waiting until the first has not finished

PROBLEM: The problem comes when I do the test using the same page ...
that is, if two or more users enter the page to perform all these
steps ... nobody respect the lock ....

I can not understand where the problem is ...
someone would help me
thanks

On 2/6/2011 6:53 AM, armando wrote:
First of all, NEVER lock tables across web pages. What happens if, for
instance, someone displays the second page then closes his/her browser?
Or any of hundreds of other things which can go wrong.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex (AT) attglobal (DOT) net
==================

armando <armando.cazzetta (AT) gmail (DOT) com> wrote:
I'm sorry, but I don't see what exactly you do. Besides that table
locks have nothing to do with commit/rollback.

It sounds as if you try to keep a lock and/or an open transaction
between different HTTP requests. This won't work, because the web
server normally does not keep a database session between requests.
Even if it would - it cannot reliably dispatch existing sessions
to incoming HTTP requests.

If you want to use transactions from within PHP (this can make a lot
of sense) then you must either commit or rollback any transaction
before the script execution ends. If you don't, then at the end of
the script your database connection will be closed and any pending
transaction will be rolled back.

PHP also knows persistent database connections. Beware! If you use
those, then the database connections will never be closed, but you
may end with lots(!) of unfinished transactions and dangling locks.


XL