Re: column prefixes

I HATE this... I've seen it in some of the applications I've worked on and it seems way too redundant.

Use meaningful table names and meaningful column names (not to mention index names) and then use aliases in your sql to reduce typing....

Jody

On Fri, 20 Feb 1998 13:44:04 -0600, suhasu_at_hotmail.com wrote:

>Hi,
>
>Are there any pros/cons to having table identifying
>prefixes to column names???
>
>I have seen database applications where the column names in a
>table have a 2-4 letter prefix distinguishing similar column
>entities in different tables.
>Eg.
>EMPLOYEE Table
>em_employee_code (code of the employee)
>em_employee_name (name of the employee)
>em_dept_code (department code for the employee)
>em_create_date (timestamp)
>
>DEPARTMENT Table
>de_dept_code (code for department)
>de_dept_name (name for department)
>de_create_date (timestamp)
>
>Thus for a sql to obtain all employees working for
>departments whose name begins with 'SOC' we will have
>
>SELECT distinct em_employee_code
>FROM employee, department
>where em_dept_code = de_dept_code
>and de_dept_name = 'SOC%';
>
>I would rather like to use this concept but need strong
>evidences in support of it.
>Thanks in advance,
>Suhas
>
>-----== Posted via Deja News, The Leader in Internet Discussion ==-----
>http://www.dejanews.com/ Now offering spam-free web-based newsreading
Received on Sat Feb 21 1998 - 00:00:00 CST