Re: Need To Dummy-Down Oracle

Time to be careful about words.

Owner and Schema in Oracle are interchangeable. They tend to be the equivalent of database in MS SQLServer and Sybase. Fieldnames must be unique within a table but can occur multiple times within an owner.

EMP_ID (which seems to be a field we are using), can appear in every table someone owns. The Referential integrity has to be identified as a constraint (Foreign Key, etc) in the DDL, though, for it to kick in. They can be temporarily disables using the 'Alter'.

Circular foreign key references have been the bane of DBAs for the 28 years I have been playing with databases (A->B->C->A). Wheeeeeeeeeeeeeee!

In article <eEz8iTTI#GA.325_at_nih2naab.prod2.compuserve.com>,   "Doug Stone" <dstone_at_res-q.com> wrote:
>
> 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?
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Mon Dec 07 1998 - 14:09:26 CST