Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Field naming conventions
Message
From
18/02/2008 16:20:56
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01293572
Message ID:
01293600
Views:
20
>As a preference... in your field names... do you include the type as part of the description...? even if you are using Hungarian notation...? such as...
>
>tstarttime vs tstart
>dduedate vs ddue

As I see it, it depends on a few things:

1. Whether you use Hungarian prefixes in column names. This is a Fox-specific thing, I've never seen it in any other type of backend. If the people viewing column names are Foxers they will probably understand the prefixes, but they are questioned by non-Foxers.

2. When not using Hungarian the philosophy is often to name the column descriptively, as accurately and unambiguously as possible. This usually does not include the column type.

3. When I've used Hungarian prefixes in column names I don't include the type as well i.e. I'd use tStart rather than tStartTime (or tStartDateTime). When I see Hungarian prefixes, in my head I translate them as
tStart = DateTime.Start
dDue = Date.Due

* so IMO putting in the type as well is redundant.
I get the impression Hungarian prefixes for column names are falling out of favour amongst Fox developers, especially those exposed to other backends. I find it useful for reading code and debugging, but I use it only for Fox, and not always then, either.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Previous
Reply
Map
View

Click here to load this message in the networking platform