Markus Schaber <[EMAIL PROTECTED]> writes:
> Antal Attila wrote:
>> Is it BUG, or FEATURE? Has anybody got good ideas for solve this problem?
> It is a feature.
Right. Note that one possible answer is, after you make the temp table,
to create a temp view referencing the temp table (and hiding th
Hi, Antal,
Antal Attila wrote:
> CREATE VIEW a_view AS SELECT * FROM a JOIN actual_code AC ON (a.code =
> AC.code);
Here, you bind the View to the permanent table.
> CREATE TEMP TABLE actual_code AS SELECT 23::INT4 AS code;
And here you create the temp table that will hide the permanent table.
Antal Attila wrote:
Hi!
I found a problem with the views in PostgreSQL if I want to use
temporary tables in it. See the next case!
[snip]
The problem is that the view use the original permanent table, but the
1) query use the temporary actual_code table.
I read the temporally table definitio
Hi!
I found a problem with the views in PostgreSQL if I want to use
temporary tables in it. See the next case!
CREATE TABLE a(, code INT4,...);
INSERT INTO a(...,code,...) VALUES (...,23,...);
CREATE TABLE actual_code(code INT4);
If I execute the next query, the result is empty.
SELEC
