| Mailing List | | Home | | MySQL General - General MySQL discussion | | MaxDB - Everything about MaxDB, formerly known as SAP DB | | MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP | | MySQL++ - Programming with the C++ API to MySQL | | ODBC - ODBC with the MySQL Connector/ODBC driver | | Java Help - Mostly related to the MySQL Connector/J driver | | Perl - Perl support for MySQL with DBI and DBD::mysql | | GUI - MySQL GUI Tools | | Announcement |
|
|
  | |  | lock collisions | lock collisions 2004-03-19 - By Jos? Rómulo Elías Contreras
Back Thanks by your help.
Jos?Rómulo Elías Contreras Ingeniero en Sistemas Computacionales Guadalajara, Jalisco Tel: (33) 3126-47-81 y 3126-48-13 Cel: (311) 910-50-59
>From: "Zabach, Elke" <elke.zabach@(protected)> >To: 'Jos?Rómulo Elías Contreras' <jromuloe@(protected)>, >maxdb@(protected) >Subject: RE: lock collisions >Date: Fri, 19 Mar 2004 11:49:22 +0100 > >Jos?Rómulo Elías Contreras wrote: > > > > > Hi: > > > > In a connection with isolation level 0, I put an > > exclusive lock to a > > row. Another connection with the same isolation level can > > read this row if > > the transacion of the first connection is not finished? > >It is the definition of isolation level 0 (read uncommitted) to be able >to READ data no matter if it is committed/rollbacked/locked/not locked. >--> yes, reader with isolevel 0 can read it. > > > > > What are the posibles collisions that can happen in > > connections with > > isolation level 0, if in the update staments I put an > > exclusive lock for > > each row that will be update? > >The others with isolevel 0 will not be able to update/delete >this row, to SELECT..FOR UPDATE when this row would be selected, >will not be able to lock (no matter if share or exclusive) the specific >row or the whole table and will not be able to change the table definition >for the specific table with some DDL (ALTER TABLE for example, CREATE >INDEX). > >Elke >SAP Labs Berlin > > > > > Thanks > > > > Jos?Rómulo Elías Contreras > > Ingeniero en Sistemas Computacionales > > Guadalajara, Jalisco > > Tel: (33) 3126-47-81 y 3126-48-13 > > Cel: (311) 910-50-59 > > > > __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __ > > MSN. Más Útil Cada Día http://www.msn.es/intmap/ > > > > > > -- > > MaxDB Discussion Mailing List > > For list archives: http://lists.mysql.com/maxdb > > To unsubscribe: > > http://lists.mysql.com/maxdb?unsub=elke.zabach@(protected) > > > >-- >MaxDB Discussion Mailing List >For list archives: http://lists.mysql.com/maxdb >To unsubscribe: >http://lists.mysql.com/maxdb?unsub=matt.woods@(protected) >
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __ Únete al mayor servicio mundial de correo electrónico: http://www.hotmail.com
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/maxdb?unsub=mysql@(protected)
|
|
 |