| From: | "John Lim" <heyjohnlim(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pl/pgsql and global variables |
| Date: | 2003-04-10 10:09:28 |
| Message-ID: | b73fmr$2m8f$1@news.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks for all the answers.
To summarize, session variables are available for TCL/Python, but not
PL/PgSQL.
Unlike Oracle, there are no "global application variables", just store data
in a table.
Tom Lane also mentioned that the pgSQL language is the most tested.
Cheers, John
"John Lim" <heyjohnlim(at)yahoo(dot)com> wrote in message
news:b70vmt$uhp$1(at)news(dot)hub(dot)org(dot)(dot)(dot)
> Hello,
>
> We are trying to select which procedural language to use with postgresql.
We
> are familiar with oracle and PL/SQL and were pleased with the close match
> with PL/pgSQL.
>
> However we need access to global variables in PL/pgSQL. I cannot find any
> mention of this in the docs. A search on google was not helpful as it just
> pointed back at the docs. Is this feature available, or do we have to use
> some of the other available languages such as PL/TCL or PL/Python?
>
> Also any advice on the stability of any of the PL/languages would be
> appreciated.
>
> Thanks again for reading and answering this.
>
> John Lim
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lincoln Yeoh | 2003-04-10 10:10:04 | Re: pg_dump / pg_dumpall / memory issues |
| Previous Message | Olleg Samojlov | 2003-04-10 09:23:12 | Re: pl/pgsql and global variables |