Thread: The problems about temporary tables in V7.3.2

Hi All

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.

Jack

"jack" <datactrl@tpg.com.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