Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Stored Procedure Naming Convention
Message
From
19/01/2015 04:27:02
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
18/01/2015 20:35:29
General information
Forum:
Microsoft SQL Server
Category:
Other
Environment versions
SQL Server:
SQL Server 2014
Application:
Web
Miscellaneous
Thread ID:
01613725
Message ID:
01613868
Views:
46
>I always put the action first so it mimics method names. And I never use an underscore. It doesn't make it easer to read and is extra keystrokes.

I learned to love underscores when I was on a VAX... and stayed so in all cases when the thing named could lose case. Naming things in camelcase is all fine if they're guaranteed to keep the case; if the system loses it, you get a word which looks like one of those long german or hungarian composite words (elektromotorotekercselés was 12m long and 1m high, on a fence - means "rewinding electric motors").

I could go with either, for all those cases when having spaces inside is impossible (hey, Cobol allowed dashes inside, that wasn't too bad), but since it's usually a mix since people on the team tend to come with different habits, the trouble is not so much readability, it's trying to remember which one was used in each case. Was it VeryLongWord or very_long_word? Ummmm... Thankfully, this led to invention of intellisense :).

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform