Re: CamelCase For Procedures Names
From: Norman Dunbar <oracle_at_dunbar-it.co.uk>
Date: Tue, 22 May 2012 15:57:33 +0100
Message-ID: <4FBBA95D.8020809_at_dunbar-it.co.uk>
I haven't been following along too closely on this thread, but I have to say that I actually like camelcase (or should that be CamelCase?) as I find it more readable that separating words with underscores.
Date: Tue, 22 May 2012 15:57:33 +0100
Message-ID: <4FBBA95D.8020809_at_dunbar-it.co.uk>
I haven't been following along too closely on this thread, but I have to say that I actually like camelcase (or should that be CamelCase?) as I find it more readable that separating words with underscores.
However, having said that, the need to use double quotes to retain CamelCase (sorry!) in databases/SQL/PL-SQL is a monumental PITA and is seriously best avoided.
I think there are two things that conspire to give me grief in the database world:
- The standard for surrounding case sensitive identifiers in double quotes;
- Vendors and/or developers who use tools for database "design" and who don't know how to turn off the default setting of "wrap everything in double quotes regardless"
- Java.
(Ok, three things!)
(Ok, at *least* three things!)
So, while I use CamelCase in many places, and save myself a character every time I don't use an underscore - handy when name length is limited - I am able to work to whatever standards are in force wherever I happen to be contracting at the time.
Just my £0.02.
And finally, I haven't got a clue what Joel said!
> *춷¬¦‰ìyªiyªÞv)í…éb²Ö¬‚&Ûz¸¬‡ÿÿ²‹kɨŠÀ‡û"š)Z¯óbqëh±çÿü‡â ....
Cheers,
Norm.
-- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767 -- http://www.freelists.org/webpage/oracle-lReceived on Tue May 22 2012 - 09:57:33 CDT