You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Directions EMEA event inspired me to add some rules for applying best pratice in the area of performance. This isn't about Lintering exactly anymore, but I guess it could be a part of the LinterCop anyway?
One of there would be to always replace the LockTable with a IsolationLevel.
Does anybody known an scenario where we still need a LockTable in favor of the IsolationLevel?
procedure WithLockTable()var
ItemLedgerEntry: Record "Item Ledger Entry";
begin
ItemLedgerEntry.LockTable();
ItemLedgerEntry.FindLast();
// Some Code hereend;
procedure NoMoreLockTable()var
ItemLedgerEntry: Record "Item Ledger Entry";
begin
ItemLedgerEntry.ReadIsolation := IsolationLevel::UpdLock;
ItemLedgerEntry.FindLast();
// Some Code hereend;
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The Directions EMEA event inspired me to add some rules for applying best pratice in the area of performance. This isn't about Lintering exactly anymore, but I guess it could be a part of the LinterCop anyway?
One of there would be to always replace the LockTable with a IsolationLevel.
Does anybody known an scenario where we still need a LockTable in favor of the IsolationLevel?
Documentation: Temporarily heightening the isolation level
Beta Was this translation helpful? Give feedback.
All reactions