‎2006 Nov 23 9:04 PM
Hi Folks,
I was wondering if a Insert stament releases db table locks. For example:
1. Lock DB Table ZXX1
2. Insert to DB Table ZXX2.
Does step 2 releases the lock set in the step 1?
Thanks for your help.
Kind Regards,
Gilberto Li
‎2006 Nov 23 9:08 PM
ABAP locks are logical, not physical, so if you use an ENQUEUE function to lock a table, table updates do not release the locks. You have to use a DEQUEUE function to release the lock.
And since they are logical, not physical, the database is not enforcing the locks. It's up to individual programs to set, check and release them.
Rob
Message was edited by:
Rob Burbank
‎2006 Nov 23 9:08 PM
ABAP locks are logical, not physical, so if you use an ENQUEUE function to lock a table, table updates do not release the locks. You have to use a DEQUEUE function to release the lock.
And since they are logical, not physical, the database is not enforcing the locks. It's up to individual programs to set, check and release them.
Rob
Message was edited by:
Rob Burbank
‎2006 Nov 23 9:16 PM
Hi Rob,
Thanks for your reply.
Your answer makes sense.
Although i'm thinking if an Insert statement on ABAP is still logical and not physical and it becomes physical until a commit work. As a consequence of this, a Insert statement could release a lock?
Does this makes sense at all?
Regards,
Gilberto Li
‎2006 Nov 23 9:30 PM
Yes, I suppose it makes sense, but it's not the way ABAP works. The commit does not release the ABAP locks.
There will be physical locks at the database level, but we don't have much control over them.
Rob
‎2006 Nov 23 10:15 PM
‎2006 Nov 23 10:35 PM