Re: Naming Conventions?
Date: Mon, 23 Apr 2007 22:53:42 GMT
Message-ID: <WNaXh.120533$aG1.35464_at_pd7urf3no>
Bob Badour wrote:
> Karen Hill wrote:
>
>> On Apr 23, 3:15 pm, Bob Badour <bbad..._at_pei.sympatico.ca> wrote: >> >>> Karen Hill wrote: >>> >>>> What do you believe is the best naming convention for tables, columns, >>>> schemas and why? >>> >>> >>> The one that everybody in the organization understands well. For obvious >>> reasons. >> >> >> So there are no standards in SQL for naming? In programming languages >> there are hungarian notation (now considered bad), Camel Case, Pascal >> Case etc. >> >> For example Hungarian notation applied to SQL would look thusly: >> >> CREATE TABLE tblOrders >> ( >> colOrderNumber INT >> colPrimaryKey INT PRIMARY KEY >> );
>
>
> Who considers hungarian notation bad? And why?
>
> aside:
> Does anybody remember when the hungarian space program gets off the
> ground? Is that this year or next?
> /aside
>
> SQL has too many standards. Camel case to separate words doesn't make a
> whole lot of sense for case insensitive names.
>
> From a theoretical standpoint, names are rather unimportant. Naming
> conventions are all about applied human psychology and are more closely
> related to information architecture than database theory.
Not sure about Hungarian, but I wonder if the people who are into type theory (I'm pretty ignorant about it) would object.
(One thing I know is that I like RPN, reverse-polish-notation in my old calculators which is about how to use things rather than deciding how to use things because of their names. When a system breaks, ie., when the rubber meets the road, how the operations work matters a helluva lot more than what things are called. As for those calculators, I bever forgot to press the "equals" key and people always returned them after borrowing them, apparently after having got the answer unusually quickly! I'm thinking of making an RPN keyboard for my pc, not sure how many keys it will have.)
p Received on Tue Apr 24 2007 - 00:53:42 CEST