Frequently we encounter with this problem that when multiple user(transaction) tries to update a same record/row of a table at the same time, the DBMS fail to serialize the access to the record/row hence throws an error saying, 'could not serialize access due to concurrent update'.Below is the solution that can prevent this kind of data race condition.

with self.env.cr.savepoint():    
	​self.env.cr.execute("SELECT id FROM YOUR_MODEL WHERE id = %s FOR UPDATE", (ID_Of_The_Records_to_lock,))        
	#​ update Records or Any ORM Operation inside the scope

In the code above, when the code execution enters the scope of the savepoint context, we are executing a query to acquire a row level lock on some rows of the table by their ID so that no other transaction can update/modify the same records until the lock is released. The lock will be released when an explicit commit on the cursor is done or a rollback is done.

Thanks & Regards, 

Brain Station 23 Ltd. 

Mobile: (+880) 1404055226 

Email: sales@brainstation-23.com 

Web: https://brainstation-23.com/ 

Address: (Building-1) 8th Floor, 2 Bir Uttam AK Khandakar Road, Mohakhali C/A, Dhaka 1212, Bangladesh