RE: Naming Convention - server code

Guys,

So we talked about table naming conventions how about procedures, packages and functions....BTW, my organization did not want to drop type of object in name - except for tables. I know arguments against but for includes - preexisting standards and help for newer DBA's esp. during quick diagnostic exercise.

GENERAL NAMING CONVENTIONS
. Part of data model validation should be to ensure that no RDBMS
reserved words are used.
. Recommended that models be checked against these standards as soon
and as automatically as possible within design process to avoid unnecessary rework.
. Should have a common list of modifiers.
. Should have a common list of descriptors.
. Construction rules: - underscores can be used for clarity
TRIGGERS-prefix+modifier(s)+table name
FUNCTIONS-prefix+description of function STORED PROCEDURES-prefix+description - description should contain clear description of process implemented.
PACKAGES-prefix (pkg?) + description.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: Paula_Stankus_at_doh.state.fl.us

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).