I have never seen this kind of behavior from MySQL but I have seen it in the application layer (what language/framework are you using) when an application, written with little thought to the implications of race conditions or multi-processing considerations gets put under load.
On 9/13/07, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote: > Hi All, > > There are many user accessing the production server and making a lots of > mistake, running wrong query (It occurs by mistake if they don't pay > attention) . There is any tools or script which can set autocommit=0; > whenever any user logged in. OR done some thing wrong which can be revert > back. > > Regards, > Krishna > -- - michael dykman - [EMAIL PROTECTED] - All models are wrong. Some models are useful. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
