At 11/19/2001 12:27 PM (Monday), zifnabbe@... wrote:

>Is there a standard in field naming?
>
>... using a prefix or not?

I have only seen prefixes like these used in one project and I strongly
disliked them. You end up with constructs like
APPOINTMENTS.APP_APPOINTMENTID which has considerable redundancy. I would
avoid embedded prefixes like these since using the "APPOINTMENTS." prefix
is always available.

Much better to standardize on selected abbreviations for you entire
database and stick to them. For example, you might make "APP" an
abbreviation for "appointment", "CTR" for "centre", and "EQP" for "equipment".

That would yield something like:

APPOINTMENTS =
APP_ID
CTR_ID
EQP_ID
APPOINTMENT

CENTRES =
CTR_ID
CTR_NAME

(My convention is also to use underscores within identifiers which are all
caps and omit them for mixed case identifiers.)