Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Fernando Nunes — — source: Usenet: comp.databases.informix
Lukas Barton wrote:
> Obnoxio The Clown wrote:
>> Lukas Barton said:
>>
>>> Only row versioning may solve my problem.
>>>
>>
>> Or selecting the correct rows.
>>
>>
> It does not, because Informix locks also previous and next row in all
> indexes. So that the probability of locking rows that other user want to
> read is more than zero.
>
> Lukas
Err.. no... it doesn't... Unless you're using page level locking or
you're using an higher isolation level in the batch such as repeatable
read (but it this case it's what it *has* to do).
Can you create a small script showing your problem?
Check that your tables are created as:
CREATE TABLE <name>
(
<column-list>
) LOCK MODE ROW
If they're not, you can change it with: ALTER TABLE <name> LOCK MODE (ROW)
But please consider that this may use a lot more locks then what you're
used to... You may have to change your ONCONFIG parameter.
Regards.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.