RE: CamelCase For Procedures Names

From: Kenneth Naim <>
Date: Fri, 18 May 2012 18:06:05 -0400
Message-ID: <003301cd3542$6cc313d0$46493b70$>

I prefer lowercase myself as it is much more readable, using quotes all the time for mixed case makes developing more tedious and like you said isn't common in the database world. I also think it is a good reminder for the .net developers that they are no longer writing .net and need to adapt to how pl/sql should be written. There are many differences that they will have to adopt and it should start with naming. "The line will be drawn here, no further!"


-----Original Message-----

From: [] On Behalf Of Jeff Chirco
Sent: Friday, May 18, 2012 5:39 PM
To: oracle Freelists
Subject: CamelCase For Procedures Names

I am settling a debate about allowing CamelCase procedure names within a package.
For example
Procedure GetOpenProjects()
Procedure get_open_projects()
I am particularly against it and would rather have everything to be lowercase and separated by an underscore but some of my developers, mainly the ones coming from the .Net world prefer it. What are your thoughts? Do you allow it or not? I am the DBA so I have the ultimate decision but I trying to see if I am not being reasonable. In the .Net world it makes sense but in the database world nothing is case sensitive so I don't feel that it is a good use.


Checked by AVG -
Version: 2012.0.2176 / Virus Database: 2425/5007 - Release Date: 05/18/12

Checked by AVG -
Version: 2012.0.2176 / Virus Database: 2425/5008 - Release Date: 05/18/12

-- Received on Fri May 18 2012 - 17:06:05 CDT

Original text of this message