Re: schema level variables and deferrable unique constraints - Mailing list pgsql-hackers

From Andre
Subject Re: schema level variables and deferrable unique constraints
Date
Msg-id 414F0E97.9060004@abs.ee
Whole thread Raw
In response to Re: schema level variables and deferrable unique constraints  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: schema level variables and deferrable unique constraints  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Tom Lane wrote:
> Paramveer.Singh@trilogy.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: libpq and prepared statements progress for 8.0
Next
From: Tom Lane
Date:
Subject: Re: libpq and prepared statements progress for 8.0