From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | Malcolm Studd <mstudd(at)recognia(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: problem with custom_variable_classes |
Date: | 2008-09-24 23:33:27 |
Message-ID: | 16598.1222299207@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> while manual in 8.4 still states:
> "When custom_variable_classes is set, the server will accept definitions of arbitrary variables within each specified class.".
It will accept *definitions*, yes. I can't imagine why you'd think
it's a good idea to not throw error when asked for an unknown variable's
value.
The whole custom-variable thing is being abused far beyond what the
facility was intended for, anyway. Rather than allowing variables to
spring into existence like magic, what we should have is some facility
for letting session-local variables be *declared*, complete with type
(int/real/string) and other info as needed. See the archives --- this
was discussed not too long ago.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2008-09-25 01:12:40 | Re: Obfuscated stored procedures (was Re: Oracle and Postgresql) |
Previous Message | Taras Kopets | 2008-09-24 22:51:44 | Re: problem with custom_variable_classes |