Hi!
>I just meant a regular update (which might impact 0 rows) and then insert (not exists) like you are doing already.
This causes duplicate key exception if other process adds same
row to table at same time.
>--transaction still ways. Should manual locking used or is there better method.
>I don't follow what you mean.
Allow access to this table for single transaction only. Wait for exclusive lock , do update/insert, release exclusive lock.
Andrus.
