Take a look at Oracle approach:
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10759/statements_7001.htm#CJAJCDDF
I sure can't fully understand how they resolve synonyms, without
confusion. They even have public and private synonyms. I don't have
access to an installation to try it out.
I tried to make just the catalog design extendable for future. May be
not a good idea. I can rewrite the catalog mechanism if that is
preferred.
Satheesh
Daniel John Debrunner wrote:
Satheesh Bandaram wrote:
2. While I am providing implementation that allows creating synonyms
for tables and views, it is possible to extend this mechanism to
other database objects as well, like procedures or functions. Some
of the database vendors already support this.
How does that work? If I create
CREATE SYNONYM B FOR A
Does this synonym work for tables, views procedures, functions etc?
CALL B -> really is CALL A;
SELECT B() * FROM B -> really is SELECT A() * FROM A
Ie. with the same single synonym?
Thus if in in the future Derby extended SYNONYM support to procedures
and functions, then creating a synonym B would have to ensure all of
the following:
- no tables called B
- no views called B
- no procedures called B
- no functions called B
Thus the synonym namespace is really a union of the namespaces it can
map to?
Dan.
|
- Re: [PATCH] Synonym support in Derby. Satheesh Bandaram
-
