Re: Table naming conventions

> How can we be sure that the table names of our application will not
> conflict
> with the table names of other applications which our clients may also
 have?
> Options we've discovered so far include:
> 1) Run each application in its own database instance
> 2) Include a prefix on each table name to avoid common names; example
> instead
> of naming the table "company" name it "wr_company"
> 3) Fully qualify every reference to a table in selects/inserts etc by
> including the
> schema owner
 

Option 1 makes it more difficult to effectively tune the environment for best performance.
Option 2 is the one I like the best. Prefix all tables supporting an application with a code indicating the application. Option 3 creates problems if you want to use public synonyms. Received on Sat Aug 16 1997 - 00:00:00 CDT