Re: Column naming convention good or bad?

MSherrill_at_compuserve.com wrote:

>On Thu, 16 Nov 2000 20:34:39 GMT, spamfilter_at_rosinowski.de (Jan-Erik
>Rosinowski) wrote:
>
>>if you change a type from int to long (i.e. i32->i64) your clientsw
>>will break anyway if you don't change it

     Yes.

>"Select EmployeeID From Employees;" breaks if you change EmployeeID
>from int to long?

     Possible. C has different format specifications for these two.

>>huh. :-) ever seen users joining varchars with numbers?
>
>Yep. What's your point?

     What is the result of such an operation?

>>types are not a storage detail but a domain classification.
>
>Exposing the domain classifications "int" and "long" through a column
>name is a storage-level detail.

     Playing devil's advocate on this:

     Aren't most operations after that doing the same? If you print a field value, the formatting rules are different for many types. The valid operations differ as well.

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:

     I have preferences.
     You have biases.
     He/She has prejudices.