From: Jon Strayer Subject: Re: Informix vs. Sybase vs. Oracle vs. (gasp) MS SQL Server Date: 1999/01/01 Message-ID: <368D5DE8.BB3D9274@acm.org>#1/1 Content-Transfer-Encoding: 7bit References: <34799917.5002172@surge.sfs.com> <347A8F21.825910FA@echonyc.com> <347B239E.CF0485C6@strengur.is> <347BCB78.1025@agd.nsw.gov.au> <347C3888.739683DD@NOSPAM.King.of.MyDomain.NOSPAM.Segel.com> <347D3DF3.54DE@agd.nsw.gov.au> <34849ab2.420767000@elf.bri.hp.com> <3482AEE8.7538BEB2@NOSPAM.King.of.MyDomain.NOSPAM.Segel.com> <3482e79b.12749721@nntp.best.ix.netcom.com> <348374A2.540C@agd.nsw.gov.au> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: IQuest Internet, Inc. Mime-Version: 1.0 Newsgroups: comp.databases.informix,comp.databases.sybase,comp.databases.oracle,comp.databases.informix Anthony Mandic wrote: > > Gary L. Burnore wrote: > > Tell the airlines that row-level locking isn't important. If the entire > > seating table for a flight was locked for one attendent to assign you a seat, > > it'd be caos. > > Thats a table lock. Any programmer who does this deserves what'll > happen to him/her. If table level locking is prefered over page level locking then why isn't row level locking preferable to page level locking? > > Row level locking is quite important in some instances. I also agree with his > > statement that to defend Sybase by saying that YOU don't think row level > > locking is important is silly. > > I thick the claims being made are specious without any hard > evidence to back them up. I have yet to see any. Can you or > anyone else provide a concrete example? It seems to me that this is the kind of question that should be answered in a good text book that also gives a big O kind of formula to tell when you need one or the other.