Re: Need To Dummy-Down Oracle

From: Doug Stone <dstone_at_res-q.com>
Date: Sun, 6 Dec 1998 08:26:38 -0800
Message-ID: <eEz8iTTI#GA.325@nih2naab.prod2.compuserve.com>

mpir_at_compuserve.com wrote in message <74c3es$rtm$1_at_nnrp1.dejanews.com>...
>Column names only have to be unique within the same table. What you may be
>asking is to disable the foreign key constraints between the tables.
>Dangerous.
>

Thanks for the feedback. Yes, if Oracle does not allow, for instance, emp_id to appear, unlinked, in multiple tables, then I wondering if there is a way to globally disable the 'duplicate column check'.

>Could the powerbuilder problem be that you are not qualifying the field
names
>such as 'owner.table.field'?
>

Since our SQL has to run in different vendor's environments (Sybase, Oracle, etc.), our practice has been to not include the table's owner in SQL statements. That practice has not caused a problem.

Would we benefit by specifying an owner in our SQL/DDL, and requiring our customers to have our product's tables owned by that owner name? Received on Sun Dec 06 1998 - 10:26:38 CST