| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "jack" <datactrl(at)tpg(dot)com(dot)au> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: The problems about temporary tables in V7.3.2 |
| Date: | 2003-05-29 01:11:58 |
| Message-ID: | 12585.1054170718@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"jack" <datactrl(at)tpg(dot)com(dot)au> writes:
> A view is created with a normal table xx without a schema specified. And
> before using the view, a temporary table xx , which has the same name as the
> normal table xx used by the view. In the same connection session, it
> supposes the view would read the temporary table. But actually it always
> reads the normal table instead of temporary table. The same thing happens to
> the table specified with a schema. If a SELECT statement uses a table with a
> schema specified, the SELECT statement won't read the temporary table when
> it exists with the same name. I just wonder the schema feature just removes
> the access priority of the temporary tables.
This is all the intended behavior.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mona Shah | 2003-05-29 09:08:26 | unsubscribe |
| Previous Message | jack | 2003-05-29 00:17:56 | The problems about temporary tables in V7.3.2 |