Re: [QUARANTINE] Re: CamelCase For Procedures Names

From: Andy Klock <>
Date: Mon, 21 May 2012 11:43:11 -0400
Message-ID: <>

Not easy :)

Another initiative we implemented was PLDOC A much harder thing to do with larger teams running a lot of historical code, but completely useful (especially in regards to avoiding reinventing the wheel constantly). We'd made the switch to PL/SQL Developer which has a pluggin for it. Since code is always documented :), why not externalize it? I spoke with Steven about this a few years ago at NYOUG and we discussed the difficulties of getting PLSQL developers to embrace this type of documentation. Oracle's SQL Developer uses PLSQLDoc (PLDOC is sort of dead) so maybe it is getting some legs. And criticism aside, .NET and Java developers are very attune to documenting their code this way, so maybe this will be an asset in your shop.

Other than my own side projects, I don't do much development anymore since I made the switch to being a Pythian DBA so I'm out of touch with what the PLSQL dev community is doing these days. (Other than troubleshooting the community's code that is ;) )


On Mon, May 21, 2012 at 11:21 AM, Jeff Chirco <> wrote:
> I wish I could get the .Net developers out of the database all together but that wont happen.

Received on Mon May 21 2012 - 10:43:11 CDT

Original text of this message