*********** REPLY SEPARATOR ***********
On 11/01/2003 at 1:29 PM Mark wrote: >Gee, I hope there is no such thing as a timeout value for "Lock Tables". >:) >If two of my programs decide that one of them needs to wait for the other, >however long that may take, then I hope MySQL honors that chosen symbiosis. >I hope it behaves like a Perl flock(): it just waits, and waits, and >waits -- and that is how I want it. :) H'mm. If this is so then how do you give feed back to a user when files are locked. Scenario: User 1 locks files for a long running job. User 2 logs on, then try's to lock files but can't because user 1 already has the lock. If there is no timeout value then the program for user 2 will just appear to hang. How do I give feed back to user 2 to say something like: "Unable to lock files after waiting 60 seconds, try again later" or whatever. IE I would like the program to be able to return control after a specific amount of time if the lock is not satisfied (I would think MySql would give an error message) in order to give feedback to the user, rather than the the program just wait and appearing to hang. This behavior occurs with record locks using InnoDB files. I would have thought a similar approach would have applied to File locks? Thanks Clyde England --------------------------------------------------------------------- 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
