Skip site navigation (1) Skip section navigation (2)

Re: schema level variables and deferrable unique constraints

From: Andre <andre(at)abs(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Paramveer(dot)Singh(at)trilogy(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: schema level variables and deferrable unique constraints
Date: 2004-09-20 17:08:39
Message-ID: 414F0E97.9060004@abs.ee (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Paramveer(dot)Singh(at)trilogy(dot)com writes:
> 
>>Oracle has package level variables which are not mappable to any postgres 
>>equivalent.
>>could we have something like schema scope variables which could be 
>>directly referred from let's say plpgsql functions?
>>Can someone give me some pointers on how to go about implementing this?
> 
> 
> It seems more appropriate to me to store your values in a table
> (variable name and value).  I don't see any strong need for a
> system-level facility for this.
> 
Package variables are not transactional, additionaly they are
session based - each session has it's own variables(values).
You can assign initial(defult) values in package spec.
Using table for them would also imply several columns
for each datatype or several tables for them.

Andre

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-09-20 17:24:47
Subject: Re: libpq and prepared statements progress for 8.0
Previous:From: Tom LaneDate: 2004-09-20 17:05:40
Subject: Re: libpq and prepared statements progress for 8.0

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group