I would strongly recommend a table prefix as opposed to a suffix as you mention at the end of the first paragraph. That was when you list the tables, all tables for a given app/module are listed together, yet in alphabetic order. With a suffix, the table names will get dispersed among the table names from other applications.
my inflation adjusted 17 cents :) ----- Original Message ----- From: "Richard Emberson" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, November 23, 2004 10:20 AM Subject: Re: table prefix > Our application has both tables that we have created and tables from > more than one external application, such a Slide. So how to keep table > names from colliding? One way of course is to create a different > database per section of one's application. Another is for each > creator of tables to assume that they will exist in a federated > system and thus they should take the effort as a good citizen of that > federation to make sure their table names are unique - one way to > do this is with a "namespace" suffix. > > Some in our group believed that they were the center of the universe > a could pick whatever table names they wished. Those with more > experience with integrating multiple separate software parts into > a whole knew that such belief were folly and lead to madness. > > Richard > > James Mason wrote: > > Not that I know of. That particular issue was resolved by creating the > > tables with a non-system user. In Oracle, that puts the tables in the > > default schema of the user (versus the System schema). > > > > Is this a feature that you need? > > > > -James > > > > On Mon, 2004-11-22 at 13:30 -0800, Richard Emberson wrote: > > > >>A little while ago someone was suggesting that they were working on > >>adding a feature that would allow one to specify a database table > >>prefix (to be used by all Slide tables) which would be used both by the > >>initialization sql and the java code. > >> > >>Is that work happening? > >> > >>Thanks. > >> > >>Richard > >> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > This email message is for the sole use of the intended recipient(s) and > may contain confidential information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all > copies of the original message. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
