From: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: table variables |
Date: | 2006-05-23 13:48:42 |
Message-ID: | e4v0fc$17jj$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I agree that the best situation would be to fix the temp tables so they
get replanned each time and therefore don't get converted to an oid.
However, now they are not fixed and I need my application to work. I was
hoping the table variables already existed, not as a request for an
additional feature.
Sim
Martijn van Oosterhout wrote:
> On Thu, May 18, 2006 at 01:16:02PM +0200, Sim Zacks wrote:
>> What I am trying to do is write a multi step query, where it would be
>> much much much more efficient to create a temp table, so a single insert
>> and then populate it with update statements.
>> The problem is that you can't use a temp table in functions without
>> dynamic execute statements, and those don't work for other parts of the
>> code (besides the fact that they're confusing).
>
> I'm thinking that we should just make temp tables work normally in
> functions. Needs no new syntax and is what people expect anyway.
>
> Have a nice day,
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-23 13:49:25 | Re: FUNCTION returns SETOF |
Previous Message | Dave Page | 2006-05-23 12:17:51 | Re: [SQL] some error when executing query in pgAdmin tool |