Re: Suggestions for naming conventions

From: Ian Ledzion <ian.ledzion_at_lgxbow.com>
Date: Tue, 24 Apr 2001 09:36:51 +0200
Message-ID: <9c3ae2$99b$1@rex.ip-plus.net>

You should be aware that Oracle is case-insensitive when it comes to DB objects, so a name like orderHeader will become unreadable, so you would have ORDER_HEADER instead.

The convention I have evolved is to prefix each table or view with a code for the system area, followed by a T or V, followed by the name. I give each table a unique 2-4 letter code which is used to prefix each column. I might be a bit over the top, but the development team finds it makes their work easier.

A few examples (from a financial app) are:

CUR_T_CURRENCY with columns CUR_IDENTIFIER, CUR_CODE, etc
JOB_T_JOB_SERVER: JBS_IDENTIFIER, JBS_CODE, ...
JOB_T_JOBQ with columns JQ_IDENTIFIER, JQ_STATUS, JQ_JOB_SERVER
JOB_V_JOBQ (view), JQV_IDENTIFIER, JQV_STATUS, JQV_SERVER_CODE,

Hope you get the idea.

<knighthing_at_hotmail.com> wrote in message news:3ae49431.3379158_at_enews.newsguy.com...
> I have been asked to come up with naming convetions for an Oracle
> database.
>
> Unfortunately, I'm a SQL Server DBA who's just been thrown into the
> Oracle beast last week.
>
> Any suggestions would be greatly appreciated.
Received on Tue Apr 24 2001 - 02:36:51 CDT