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
I activated this rule today, it seems to be checking the underlying table and not the actual buffer being used:
block-level on error undo, throw.
define buffer customer for customer.
define buffer bucustomer for customer.
find first customer no-lock no-error.
for each bucustomer
where bucustomer.custnum > 0
and customer.custnum > 0
no-lock:
// false positive on buffer usage customer.custnum > 0
end.
The text was updated successfully, but these errors were encountered:
gquerret
changed the title
FP: Check that buffer is correctly accessed in WHERE clause
Check that buffer is correctly accessed in WHERE clause
Oct 12, 2023
I activated this rule today, it seems to be checking the underlying table and not the actual buffer being used:
The text was updated successfully, but these errors were encountered: