Re: Archaic Table Names. Frowned upon Synonyms

From: Mark Cudmore <mcudmore_at_kamloops.env.gov.bc.ca>
Date: 1998/03/13
Message-ID: <1998Mar13.142648.10032_at_vmsmail.gov.bc.ca>#1/1


[Quoted] You poor soul! I couldn't imagine having to deal with such cryptic names, it makes everything from maintenance to upgrading a nightmare.

Here are just a few reasons off the top of my head why archaic names are terrible:

  1. New employees can remember the english names easier and faster.
  2. Maintenance becomes a nightmare, trying to keep all these names straight in your head
  3. Totally makes an audit of the institution more difficult by regulating bodies
  4. Total non-compliance with ISO-9000 standards
  5. Technological step backwards

That's is just a few reasons, besides the fact that it is totally asthetically offensive!

Geez! Mark

Adrian Hodson wrote in message <6ec7l0$7bm$1_at_peuplier.wanadoo.fr>...
>At the bank where I work a typical table name is called TPF47 or PFM16 and
>synonyms are frowned upon - they are said to make debugging of problems
 more
>difficult!!!!!!!
>
>Reasoned argument has had no effect on the DB2 administrators that admin
>Oracle as a side line.
>
>Reaction please. (As much as possible - I want to be able to take in to
 work
>a printout at least as long as my arm).
>
>Adrian Hodson.
>
>
>
>
Received on Fri Mar 13 1998 - 00:00:00 CET

Original text of this message