Re: PL/SQL Code Reviews

<redrobot5050_at_gmail.com> wrote in message news:1126795592.760956.139350_at_g49g2000cwa.googlegroups.com...
> Guys,
>
> Thanks for the advice. ....

> Things we want to keep in mind:
> 1) We will probably move to 10g, so eliminating any deprecated
> functionality from 9i is going to be important

Do you have a lot of PL/SQL? An automated tool that simply pointed these out might be of use.

> 3) Style is inconsistent because we still argue about what is "most
> readable" or "proper format" for PL/SQL syntax. (*not trying to start a
> flame war here*)

Why not use a source code formatter to fix the style so they are all consistent?
See www.semdesigns.com/Products/Formatters/PLSQLFormatter.html.

> 3) There is still some of a "if it isn't broke, don't fix it mentality"
> going on in the development team. We know that trying to condense the
> code into something more elegant could be an ugly, uphill battle at
> first. And something like that would require a full systems test by the
> QA team, which is swamped with last-minute items before we "go-live"

We are completing a PLSQL test coverage tool. That would at least tell you if the QA team has tested everything. We are looking for Beta testers of that tool.

-- 
Ira D. Baxter, Ph.D., CTO   512-250-1018
Semantic Designs, Inc.      www.semdesigns.com