From: Richard Yates Subject: Re: Naming Convention for Columns Date: 1998/03/17 Message-ID: <350ED019.15C3@open.ac.uk>#1/1 Content-Transfer-Encoding: 7bit References: <6dnbes$6r5@newsops.execpc.com> <3505ad61.266543@read.news.global.net.uk> <80MTKDA1rxB1EwQD@jbdr.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Nugatory. Newsgroups: comp.databases.sybase,comp.data.administration,comp.databases.ibm-db2,comp.databases.informix,comp.databases.ingres,comp.databases.ms-sqlserver,comp.databases.oracle.server Neil Warnock wrote: > In article , > Michael Leo wrote: > >Jeremy Rickard writes: > >> In article <3505ad61.266543@read.news.global.net.uk>, Keith Boulton > >> writes > >> >Having said that, I did work for an organisation once which had DB2 > >> >naming conventions where table and column names were limited to 8 > >> >characters. The first three characters were a system mnemonic, > >> >followed by a five digit number i.e. select xyz00024, xyz00057 from > >> >xyz11003. > >> That's nothing! I worked for an international (US based) company which > >> had one system with 4 character column names. These were abbreviations > >> of the full attribute names - in Norwegian, naturally. > >Hah! > >I once worked for a company that re-used bits that fell out of the > >ends of disconnected cables. If you got your weekly status > >reports in late you were chosen to sort them into piles of '1's > >and '0's. > I'd fire anyone who pulled that kind of s**t working for me. I've got > enough problems using alpha characters without having to worry about what > table/column 01010100 00110011 00101110 01000011 00110100 00110111 > refers to. Pshaw, you think that's something? I'd personally sack, set fire to, and jump up and down on the ashes of whilst swearing loud oaths anyone who created a database product with underlying file names such as aaaaaaab.t00 aaaaaaac.t00 aaaaaaad.t00 aaaaabaa.t00 and that is *just for starters*! Ooh-err. Or something. Richard. -- My newsfeed is erratic :. post+e-mail to be sure I receive your msg. The Open University is not responsible for content herein, which may be incorrect and is used at reader's own risk.