Taras Kopets wrote:
now you have to initialize this variable once per session before usage:
SELECT set_config('olap.rownum_name', false);
Ok, thanks. That has fixed my problem.
Malcolm
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription
On Wed, Sep 24, 2008 at 07:33:27PM -0400, Tom Lane wrote:
> 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.
because this is how it worked.
i'm not saying it was good. it worked that way, and int
hubert depesz lubaczewski <[EMAIL PROTECTED]> 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 g
On Thu, Sep 25, 2008 at 12:38 AM, hubert depesz lubaczewski
<[EMAIL PROTECTED]> wrote:
> but it means that there is currently no way to check if there is value in this
> - i.e. if it has been initialized.
now you have to initialize this variable once per session before usage:
SELECT set_config('o
On Wed, Sep 24, 2008 at 12:15:41PM -0400, Malcolm Studd wrote:
> I have a pl/pgSQL function[1] to calculate row numbers (based on [2]).
> It uses a custom variable. This was working earlier, but is breaking now
> saying it can't recognise the variable. The custom_variable_classes is
> set in
Hi,
I have a pl/pgSQL function[1] to calculate row numbers (based on [2]).
It uses a custom variable. This was working earlier, but is breaking now
saying it can't recognise the variable. The custom_variable_classes is
set in the postgresql.conf.
pgdb001=> select rownum('') from generate_ser
