John Singleton wrote:
>
> Elke,
>
> >Yes, DDL does not perform name resolution
> >
> >
> All DDL statements? Some, like DROP TABLE seem to perform resolution at
> least on the first level...
Of course all commands check for private tables/views/synonyms without specifying the
owner/schema for t
John Singleton wrote:
> >
> >
> >It looks nearly correct.
> >But public synonym would not be level 4, but level 2, increasing the
> levels of search in dba2 and dba.
> >
>
> Hurm. Okay, then how does it find something like this?
>
> Catalog:
> Users:
> DBA.DBA
> DBA.DBAUSER (RESOURCE)
> DBA.DBA2
Elke,
Yes, DDL does not perform name resolution
All DDL statements? Some, like DROP TABLE seem to perform resolution at
least on the first level...
Cheers,
JLS
Zabach, Elke wrote:
John Singleton wrote:
Hello all,
So I think I've pretty much got MaxDB's name resolution system down. But
I jus
It looks nearly correct.
But public synonym would not be level 4, but level 2, increasing the levels of search
in dba2 and dba.
Hurm. Okay, then how does it find something like this?
Catalog:
Users:
DBA.DBA
DBA.DBAUSER (RESOURCE)
DBA.DBA2 (DBA)
DBA2.USERDBA2 (RESOURCE)
Objects:
DBAUSER.SOMETABLE
John Singleton wrote:
> Hello all,
>
> So I think I've pretty much got MaxDB's name resolution system down. But
> I just wanted to post to the list to make sure :)
>
> So, from what I've been able to determine, it works like this:
>
> 1) Say I have three users. DBA, DBA2, and DBA2USER. DBA creat
