New Rule: no obsolete jump statements about plsql-and-sql-coding-guidelines HOT 3 CLOSED

An unconditional continue does not make sense at all...but other usages of continue are ok imho. Otherwise you would have either:

• lenghty if / else constructs
• raises and exception handler to skip an iteration
  and here continue is much easier

from plsql-and-sql-coding-guidelines.

If we say we should not use GOTOs (see G-4310) and RETURNs (see G-7430) only at the end of a function, then we should also avoid using CONTINUE.

Hence I'm thinking about changing the rule to not use CONTINUE at all. Thoughts?

from plsql-and-sql-coding-guidelines.

So you suggest to change the rule to

Never use unconditional CONTINUE statements

Right? Do you have a good example where CONTINUE makes sense?

from plsql-and-sql-coding-guidelines.