[zcodescan.cobol.rules.SqlWhereRule] Distinguish the case of DECLARE CURSOR FOR SELECT from the case of simple SELECT

[FALLAI-Denis]

Description of the enhancement requested

The zcodescan.cobol.rules.SqlWhereRule rule allows you to control the presence of a WHERE clause in a SELECT, DELETE, or UPDATE SQL query.

While a WHERE clause is generally required in a simple SELECT query, this is not necessarily, and often is not, the case in a CURSOR FOR SELECT query, which can process an entire table (especially in batch processing).

The zcodescan.cobol.rules.SqlWhereRule rule should also be able to handle the CURSOR FOR SELECT query independently of the simple SELECT query.

It should also be considered whether there are other SQL statements that need to be handled, such as MERGE.

Thanks.

[Spratima]

We will analyze the issue you have pointed out and will get back to you with an update. Thank you for bringing this to our attention.

[FALLAI-Denis]

Hi,

It should also be noted that the severity is the same for all SQL statements. Perhaps different severities should be used depending on the statement.

In particular, for a DECLARE CURSOR FOR SELECT statement, the severity could be INFO, while for a simple SELECT statement, the severity could be BLOCKER.

If the severity cannot be modulated within a rule, then perhaps a separate rule should be created for each SQL command.