Hello,
I have installed the Mysql Max version with DBD tables (3.23.40) and is
running the server on NT. I have a rather small database with lots of
tables (22) and liked the idea with transactions. This is my situation:
I have one application writing and reading data from my tables (using
transactions) and other applications that reads the data that is
committed. Now, I just found out that while one application is doing a
transaction the other applications can't even read data from the tables
and is just hanging in their database call. This is very unfortunate
since it can be hanging in the call for some time and until it is
released the program can't continue executing. I've read about the page
locking in DBD, is this the behaviour of that? It seems very weird that
one application must wait for another applications commit and not at
least get the last "good" data from the database. Why using transactions
in that case? I could just lock all tables, do my changes and then
release them, which in my case is unthinkable so I must use "dirty" data
and live with the inconsistency in the database.
Please, does anyone know of a workaround or a variable for the server or
something that can be done to ensure reading without hanging while using
transactions?
Very grateful for help,
/Monika A-J
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
