From: Richard Huxton <dev@archonet.com>
To: <sbiswas@cisco.com>, <pgsql-sql@postgresql.org>
Subject: Re: FW: Function
Date: Tue, 17 Feb 2004 19:26:35 +0000
User-Agent: KMail/1.5
References: <00e601c3f564$2dca6740$2a154d0a@apac.cisco.com>
In-Reply-To: <00e601c3f564$2dca6740$2a154d0a@apac.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402171926.35935.dev@archonet.com>

On Tuesday 17 February 2004 14:41, Sumita Biswas (sbiswas) wrote:
> Is there nothing like SET NOCOUNT ON; in plpgsql

What is this supposed to do for you?

> Is there any option like SET ANSI_NULLS ON in plpgsql.

What is this supposed to do for you too?

> Do we append # before the temp table names in plpgsql, like we do for
> MSSQL ? In case no how do we create a temp table in a function in plsql?

The thing to remember with plpgsql is that it's compiled (unlike say plTcl). 
This means that it translates table-names etc. into oids. So what you have to 
be careful of is referring to a temporary table that is created, destroyed an 
re-created (because it's oid will change).

The solution is to use the EXECUTE command to build a dynamic query. Check the 
archives for plenty of other people doing this.

-- 
  Richard Huxton
  Archonet Ltd