New Rule: no unused assigned values about plsql-and-sql-coding-guidelines HOT 4 CLOSED

From my point of view this should be handled by G-1030.

However, PL/SQL Cop does not report a G-1030 for my_date. I consider this a PL/SQL Cop bug. The description of G-1030 should be extended to cover this case as well.

from plsql-and-sql-coding-guidelines.

G-1030 handles variables that are not used at all. This rule handles variables, that are used (assigned a value), but having assigned a value are no more touched.

from plsql-and-sql-coding-guidelines.

I know. I'm thinking about, if this case should not be handled by G-1030 as well. The reason is, that the Eclipse IDE does not distinguish between these two cases:

from plsql-and-sql-coding-guidelines.

Based on the discussion in #22 and #40 where we tend to split a rule into multiple rules with clearer meaning and scope, I think now, that it is most probably also a good idea to distinguish between

• variables that are declared but never used (G-1030)
• variables that are declared, assigned a value, but never read (this rule)

It will help the developer to more quickly understand what is wrong. And that is a good thing.

from plsql-and-sql-coding-guidelines.