Usage of default buffer for tableName #961
ParaEnigma
started this conversation in
General
Replies: 1 comment
-
A change has been introduced in 2.15 (released yesterday), that allows you to choose scopes to be skipped. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This warning is raised when a db buffer is not defined for a table. This rule flags all references including those in the main procedure. While defining a buffer in the main procedure resolves the error, it does not resolve the reason for the error (potential scoping issues). Is it possible to run this check only for internal procedures, functions, and methods?
In the example below, I want customer scoped to the main procedure/program. Defining a buffer does not make sense in this scenario and results in false-positives.
// Main
find first customer no-lock no-error. <-- Buffer error
run checkCust:
define buffer custBuf for customer.
find first custBuf no-lock no-error.
end.
Beta Was this translation helpful? Give feedback.
All reactions