From: Tom Lane <tgl@sss.pgh.pa.us>
To: mario.splivalo@mobart.hr
Cc: pgsql-sql@postgresql.org
Subject: Re: Using Temporary Tables in postgres functions
Date: Fri, 26 Jan 2007 09:57:32 -0500
Message-ID: <23176.1169823452@sss.pgh.pa.us> (raw)
In-Reply-To: <1169808705.3045.21.camel@localhost.localdomain>
References: <1169735954.31872.38.camel@localhost.localdomain>
<20030.1169741373@sss.pgh.pa.us>
<1169808705.3045.21.camel@localhost.localdomain>
Mario Splivalo <mario.splivalo@mobart.hr> writes:
> On Thu, 2007-01-25 at 11:09 -0500, Tom Lane wrote:
>> I believe the problem is that for a SQL function we parse the whole
>> function body before executing any of it. So you'd need to split this
>> into two separate functions.
> Having two function complicates, a bit, interface between applicaation
> and the database. But, then again, If I split it in two functions, then
> one with the UPDATE still can't find temp table referenced in other
> function, right?
It can as long as the table already exists when the function is entered.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, mario.splivalo@mobart.hr
Subject: Re: Using Temporary Tables in postgres functions
In-Reply-To: <23176.1169823452@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox