 |
 |
Archives of the TeradataForum
Message Posted: Wed, 17 Dec 2003 @ 10:50:28 GMT
| Subj: | | Re: Help me understand.. |
| |
| From: | | Narayan Murthy |
Case 1 brings in the ambiguity issue because of the query context. Though! You have the default database set to dev2, you also bring in
dev1 within your query context and there by w.r.t the context of the query you have two database dev1 & dev2. Now, where the objects
that are qualified by the database name have no problem during resolution, the same causes an ambiguity issue for objects that are not
qualified if the resolver happens to find the same objects presence in the databases w.r.t context of the query (in this case we have dev1
and dev2 and the resolver finds that tab2 is found in both - thus the ambiguity error)
This would infact tell you why scenarios 2, 3 & 4 go through without any problems.
Narayan
| |
