If your application must succeed in its data edits, then pessimistic concurrency is the necessary choice. Pessimistic locking poses the greatest danger of freezing your data. At cursor creation the server locks whatever set of rows it sends to the client. The whole cursor does not receive an exclusive lock, just those records that the cursor processes at one time. Other users cannot obtain either shared or exclusive locks on this data until the cursor moves off the block of records.