I use a naming convention that I have developed over the years from various
places. It is also constantly evolving. Other people have told me that it
helps them read my code. I think any kind of convention is better than none
- consistency will help make the code more readable and maintainable.
My convention, briefly:
In the database, Stored procedures begin with SP_
Data tables begin with T_ and the data that they store, such as T_Orders or
T_States. Join/Junction Tables start with J_ and then the names of the
tables they join, such as T_States_Orders. Simple lookup tables begin with
L_. As far as my fieldnames, the only rule I use there is that the primary
key fields almost alway end with ID.
In the code: All queries start with Q_, Structures with S_, Arrays with A_,
Lists with L_, etc. When I store WDDX packets in variables I start them
with WDDX_. I name all standard variables with mixed case, such as
FirstName or SessionVars, etc.
There are a few other details, but those are the basics - it's worked well
for me.
Avi
At 10:42 AM 10/23/2000 -0600, you wrote:
>Do most of you use some kind of naming convention for your backend table
>names, queries, fieldnames, etc. I'm curious as to what the benefit is of
>using , say, the Leszynski/Reddick naming convention for a backend that the
>client never really sees anyway?
>
>I ask because in two years of database/web programming, I've never worked
>with anyone who used any kind of naming convention other than their own
>personal style. Now I find myself defending my style in NOT using a naming
>convention.
>
>Thanks,
>Erika Foster
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_community or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
