> 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@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026