Re: Global/persistent variables

I understand your pain, because PL/SQL is so close to plpgsql the functions
should just drop into quotes with renamed parameters, but they don't.
Using another language makes the port more difficult.

Have you considered functions that store the variable value in the database
and read it back from there? The functions would have to store variables
values by some kind of session or user ID so concurrent sessions wouldn't
trump one another. This would help with variable reference but variable
assignment would require more recoding.

There is also the issue of initializing sessions and cleaning up after
them. Not pretty.

Rick

Tom Lane
<tgl(at)sss(dot)pgh(dot)pa(dot)us> To: Ronnie Meier Ramos <ronnie(at)viler(dot)com(dot)br>
Sent by: cc: pgsql-general(at)postgresql(dot)org
pgsql-general-owner(at)pos Subject: Re: [GENERAL] Global/persistent variables
tgresql.org


01/06/2005 03:43 PM

Ronnie Meier Ramos <ronnie(at)viler(dot)com(dot)br> writes:
> AFAIK PG doesn't have packages - this is not a problem since I can
> handle it with different schemas or some naming convention, but is there
> a way to declare persistent variables (that would be "visible" to any
> function up to the end of the session) ?

plpgsql doesn't have this at present, but some of the other PLs do.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match