Hi Volker,

Regarding the G-7110 issue, there was already a question in the forum. See https://www.salvis.com/blog/forum/plsql-cop/initializing-nested-table-g-7110/

Regarding the G-1050 issue. 2 and ‘close cur_testvg_scorewerte’ are both literals. According to to the guideline you should consider using constants instead of literals. However, I really understand that it is too much to 100% avoid literals. So either user the NOSONAR marker to disable the check within the code ore disable this guideline check completely.

HTH
Philipp

I’m new to PL/SQL Cop and tried it on a short package for testing purpose.

There are two repeating incidents in the list and one seems to be a mistake:

On “SET tsw_tag1 = l_testvb_scorewerte(i).tsw_tag1” inside an update statement I get the error “G-7110: Try to use named notation when calling program units.” which is definitely wrong, because it is an index access to a collection.

The second error reported “G-1050: Avoid using literals in your code.” happens on two different occasions:

WHEN 2 THEN
tsp_exception.melde_debug(p_text => ‘close cur_testvb_scorewerte’);

The error is ok in principle, but within the context it should be ignored. Is there an easy way not to ignore the whole error, but only within a certain context?

Regards

Volker

Hello Friedhold,

Your welcome. First of all the table on page 8 shows a “possible set of naming conventions.”. Think of it as a starting position for your own naming conventions if you do not have them already. However, since we recommend to avoid declaring global variables public (see guideline 7230) it would be inconsistent to distinguish between public and ‘modul’ scope of global variables.

The current version of PL/SQL Cop comes with two example validators for naming conventions. One implementing the 15 guidelines on page 8 and another one with just 3 simple guidelines:

• ‘g_’ for global variables
• ‘l_’ for local variables
• ‘p_’ for all kind of parameters

I also see “in”, “out” and “io” used as parameter suffix. So, please continue to use your set of naming conventions as long as it fits your needs.

Thanks,
Philipp