From: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org, pgpsql-bugs(at)postgresql(dot)org |
Subject: | Re: order by in for loop in plpgsql does not work |
Date: | 2002-11-27 19:01:44 |
Message-ID: | 3DE51698.DFCC3CCD@nsd.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom,
At first I was about to tell you that it did not make sense to use local
variable in the order by or group by clauses, but since they (order by -
group by) can take numerical arguments...
I understand perfectly now.
Thanks for the help.
JLL
Tom Lane wrote:
>
> "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> > I'd also say your problem was probably more due to how you are initialising
> > exchangeno and routeno variables to empty strings and then using those values
> > in the order by clause of the select.
>
> Yes, this is surely the issue: the 'exchangeno' and 'routeno' names in
> the ORDER BY clause are being replaced by the plpgsql vars of the same
> names.
>
> It's a bad idea to use plpgsql variable names that are the same as
> column names of tables that you use in the function...
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Felipe Schnack | 2002-11-27 19:02:27 | table name size |
Previous Message | Tom Lane | 2002-11-27 18:50:10 | Re: query visibility - trigger order - bug? |