| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Jim Faucette | Date: | July 23 1999 8:07pm |
| Subject: | Re: locking problem...? | ||
| View as plain text | |||
elble@stripped wrote: > > hello, Sinisa. > > BTW, this works: > > client #1.) lock tables foobar read; ('READ' lock acquired) > client #2.) update low_priority foobar set this=1; (pending 'WRITE' lock, blocked) > client #3.) select * from foobar; (this doesn't block now!!!) > > i see now, it doesn't really have anything to do with locking per se. ;-) > > but, am i the only person who has this problem? > In general read and write locking is not intuitive. Whether at the system or application level it usually takes time and effort to understand get used to the 'logic'. jim...
| Thread | ||
|---|---|---|
| • locking problem...? | elble | 20 Jul |
| • locking problem...? | sinisa | 20 Jul |
| • Re: locking problem...? | elble | 20 Jul |
| • Re: locking problem...? | elble | 20 Jul |
| • Re: locking problem...? | sinisa | 21 Jul |
| • Re: locking problem...? | elble | 21 Jul |
| • Re: locking problem...? | sinisa | 22 Jul |
| • Re: locking problem...? | elble | 22 Jul |
| • Re: locking problem...? | sinisa | 22 Jul |
| • Re: locking problem...? | elble | 22 Jul |
| • Re: locking problem...? | elble | 23 Jul |
| • Re: locking problem...? | Jim Faucette | 24 Jul |
| • Re: locking problem...? | elble | 24 Jul |
| • Re: locking problem...? | Michael Widenius | 29 Jul |
| • Re: locking problem...? | elble | 29 Jul |
