The answer is quite simple: this statement was composed by several functions used for ordering on string values as also
onnumeric.
--- Thomas Kellerer <spam_eater@gmx.net> schrieb am So, 15.8.2010:
> Von: Thomas Kellerer <spam_eater@gmx.net>
> Betreff: Re: [GENERAL] Wrong "ORDER BY" on a numeric value result
> An: pgsql-general@postgresql.org
> Datum: Sonntag, 15. August, 2010 10:43 Uhr
> Stefan Wild wrote on 15.08.2010
> 10:36:
> >> column is numeric, but upper() works on text, and
> returns
> >> text, so your
> >> numeric column got casted to text by using upper
> (which is
> >> pointless
> >> anyway - there is no "upper" version of digits).
> >> remove upper() and you'll be fine.
> >>
>
> > Thank you guys! That was the point.
>
> The real question is:
>
> what did you try to accomplish with the UPPER() on a
> numeric column?
>
> Regards
> Thomas
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>