Re: Naming conventions for special database objects

Marco,

you will not find examples on naming boolean columns in "SQL
programming style" as page 42 mentiones, this data type should be
avoided. Indeed in most cases there are better ways to model the data
than with BIT columns. In cases where you can not avoid it (or choose
not to do), naming it with Is... or Has... is suggested by [Mauss
2004], [Watt 2004] to ensure that the meaning of the data is not
ambiguous. See these links:
http://weblogs.asp.net/jamauss/articles/DatabaseNamingConventions.aspx
http://justinsomnia.org/writings/naming_conventions.htm

Such convention is also used in the .NET framework (remember, it has
nothing to do with databases) for boolean values, but I could not
locate the rule for it in
http://msdn2.microsoft.com/en-us/library/ms229045.aspx

Personally I like the pascal case naming convention there what solves
the problem of acronyms and abbreviations and says that all
abbreviations with two letters are to be uppercased, such as ID or DB
and with three or more letters follow the pascal case convention, i.
e. first upper, following lower cased e.g. EanCode.

brgds

Philipp Post