From: Mario Splivalo <mario.splivalo@mobart.hr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Using Temporary Tables in postgres functions
Date: Fri, 26 Jan 2007 11:51:45 +0100
Message-ID: <1169808705.3045.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20030.1169741373@sss.pgh.pa.us>
References: <1169735954.31872.38.camel@localhost.localdomain>
<20030.1169741373@sss.pgh.pa.us>
On Thu, 2007-01-25 at 11:09 -0500, Tom Lane wrote:
> Mario Splivalo <mario.splivalo@mobart.hr> writes:
> > Am I doing something wrong here, or there is no way of using temporary
> > tables within 'sql' written functions?
>
> 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?
I have no problem writing func1() example in plpgsql, it just seemed to
me that using sql instead of plpgsql (when I actually can use sql) gives
me a little performance improvement.
Mike
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: mario.splivalo@mobart.hr, tgl@sss.pgh.pa.us
Subject: Re: Using Temporary Tables in postgres functions
In-Reply-To: <1169808705.3045.21.camel@localhost.localdomain>
* 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