Stephen, Wednesday, November 20, 2002, 5:48:35 AM, you wrote: SA> I've managed to build my first web database using MySQL and accessing SA> it with Python CGI scripts. I only have two tables going, and not SA> many columns per table, but I'm suspecting that there will be many SA> calls to INSERT, UPDATE, and SELECT.
SA> So my question is this: do I need to use explicit locking to make SA> this work well in a web environment? Or will the implicit locking of SA> MySQL handle all the dirty work? On non-transaction tables INSERT, UPDATE and DELETE set write lock on the table, SELECT sets read lock on the table. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com --------------------------------------------------------------------- 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
