Hello.
Every thing depends on logic of your application. But I don't see a big gain of using table-level locks on InnoDB. Among others this might be helpful: http://dev.mysql.com/doc/mysql/en/internal-locking.html Scott Klarenbach <[EMAIL PROTECTED]> wrote: > I've got a good deal of experience using mysql, but never in a large > production environment with many concurrent users. > > Using the InnoDB engine, what is the general practice for ensuring > data integrity when multiple users are writing to the same table? > > Should I explicitly lock the table before I write to it, or does mysql > do this automatically? > > Thanks, > sk > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
