During a debug of my app, I've discovered that in a dataset from IB_Query with pessimistic looking at true, when I start editing the first row of the grid the famous "lock dummy update" is performed, but when I then go to the second row and edit it, SQLMonitor does not show an update upon the new row anymore. Going through the code shows that the "lock process" is fired, but there is a certain condition that prevents it to be performed. The same with an explicit SQLLock or not.
Is it normal or a bug?
(BTW, how could I 'unlock' a row, after the editing is performed? Must I commit/rollback the transaction?)
thanks
IBO 4.2I, Firebird 1.0,
Transaction isolation: tiCommitted