Sybase Locking Problem

goodman

why I need this mechanism ?
actually, my app starts with more than one instance on different machine.
every instance must process same data in sequence to achieve HA.
But I don't know which instance will process the data first, I need to let only the first one instance
to process the data ( the pktest is like my latch ). The others blocked if they want to process the same data.
while theother one is processing.

I think it's not ambivalent, right ?

5个周

No,just like I always advice developers should use simple and standard ANSI SQL syntax instead of extended SQL syntax,I think we should not design our apps logic depending on DB product's own mechanism.

I am not sure about MS SQL Server and Oracle's mechanism,but I think DB is DB. So datarows lock 's base function should be useful for concurrent ,and this concurrent should not be related with the logic of data.

The ambivalent I mean is that I think your request need to join current with the logic of data.If DB product implement such future,it 's good;if don't,it's OK.