Re: Let me be the first
Lukas Barton wrote: > >> "The next release, code-named Cheetah, is due to beta this spring and >> will >> feature *record-level locking*, technology carried over from the latest >> release of IBM DB2, said Arvind Krishna, vice president of database >> servers for IBM Software's Information Management Group, Somers, N.Y." >> >> I think I speak for us all when I say: "What the *fuck*???" >> >> First of all, it's row-level locking, as any good relational database >> user >> knows. And secondly, IDS has had row-level locking since ... help me out >> here... the early 90's? >> > > Informix row-level locking makes me mad: > - locks row for reading from read_commited transaction > - locks the same way previous and next record in index > > This makes Informix quite unuseable for OLTP in comibination with batch > processing (the same time). I've had no problems writting OLTP with batch jobs simultaneously for the almost 20 years using Informix. Haven't you heard of 'SET LOCK MODE TO WAIT 10;'? Or partially committing massive updates & deletes so they do not interfere with online processing? It seems to me that rather than Informix's way of doing things being maddening it's your programming skill that are such. Well, feel releived. IDS Cheetah will have record versioning so, if you enable it, no more locking problems. Art S. Kagel
Art S. Kagel wrote: > > Well, feel releived. IDS Cheetah will have record versioning so, if you > enable it, no more locking problems. > > Art S. Kagel > Wow. That's huge. Hope it's a little better implemented than SQL Server's "tick the box" kludge.
Mark Townsend said: > Art S. Kagel wrote: > >> >> Well, feel releived. IDS Cheetah will have record versioning so, if you >> enable it, no more locking problems. > > Wow. That's huge. Hope it's a little better implemented than every > Oracle kludge. I've fixed that for you. :o) -- Bye now, Obnoxio "... no bill is required as no value was provided." -- Christine Normile -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.