Re: Column naming convention good or bad?

From: <MSherrill_at_compuserve.com>
Date: Sat, 18 Nov 2000 16:15:57 GMT
Message-ID: <3a169b89.714807_at_news.compuserve.com>

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

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

>huh. :-) ever seen users joining varchars with numbers?

Yep. What's your point?

>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.

-- 
Mike Sherrill
Information Management Systems

Received on Sat Nov 18 2000 - 17:15:57 CET

This message: [ Message body ]
Next message: gkiourtas michail: "Re: Missing entity types"
Previous message: Alan: "Re: Help about a data type"
Maybe in reply to: Ali Tajdari: "Column naming convention good or bad?"
In reply to Jan-Erik Rosinowski: "Re: Column naming convention good or bad?"
Next in thread: gkiourtas michail: "Re: Missing entity types"
Reply: Gene Wirchenko: "Re: Column naming convention good or bad?"
Reply: MSherrill_at_compuserve.com: "Re: Column naming convention good or bad?"
Reply: Gene Wirchenko: "Re: Column naming convention good or bad?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message