Trith wrote:If column X is in "some other table A in any other scheama" then it is not the same column as column X in table Y in schema Z. Regardless of what they are named, how the data is typed, how the tables and columns are structured, the tables in schema A are totally separate objects from tables in schema Z. The possible fact that they may have the same names and data types is - as far as Oracle is concerned - mere coincidence.
Thanks Brian, in your example we are creating our table.
What I wanted to know is that does Oracle really have multiple tables (similar to my example, Standard Oracle Tables) with the same columns, the life of which (data) is the same ......
In other words, If I restrict access to column X in table Y in schema Z, then is it possible for someone else to access the same column X from some other table A in any other schema S.
This thought comes out while working on Database Level Masking for Sensitive Data/Information!
Can two different Oracle tables (residing in same or different schema) have the same or similar columns (containing same or similar data) ?Simple answer is Yes.
EdStevens wrote:Yes, it made more sense 20 years ago, when all database engines were going to be standard and relational. In our terms, it's automatically creating a foreign key just 'cause the columns have the same name as a primary identifier of another table (implementing the meaning of domain in relational theory). So for example, if you have company_code at the beginning of all the tables, when you insert a row in any table the company_code has to exist. And if you define indices, the first one alphabetically is the "primary identifier". Except, there are no constraint_type 'P' when looking at dba_constraints (except for tables internal to the app). The optimizer and things like MV love that. The words mean exactly what someone else wants them to mean. Wheeee!jgarry wrote:???
The 4GL I work on implicitly creates domains based on identical column names between tables. Welcome to the future, 1992 style.
It depends on the namespace.That is what I said.
In the schema namespace, you can have different types of objects with the same name. In various hashing schemes used by oracle internally to name things, there can be collisions.Could you give an example?