From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: RE: [PATCHES] relation filename patch |
Date: | 2000-05-01 17:50:36 |
Message-ID: | 200005011750.NAA27703@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Hmm. Further perusal leads me to believe that this override is a
> standards extension, as the clause about the tablename being unique in
> the current namespace does not have an exception for temporary tables.
> Nothing wrong with that, just making it clear. What's the use/case for
> this feature? Does it come from some other DMBS?
I am quite surprised people don't like that feature, or at least one
person doesn't. If someone else creates a table, it should not prevent
me from creating a temporary table of the same name.
I know Informix doesn't implement it that way, and they complained
because a program started not working. Research showed that someone had
created a real table with the same name as the temp table.
Our code even masks a real table created in the same session. Once the
temp table is dropped, the real table becomes visible again. See the
regression tests for an example of this.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-01 18:08:30 | Re: RE: [PATCHES] relation filename patch |
Previous Message | Ross J. Reedstrom | 2000-05-01 17:44:11 | Re: RE: [PATCHES] relation filename patch |