pgsql/src/backend/utils/adt (formatting.c) - Mailing list pgsql-committers

From Bruce Momjian - CVS
Subject pgsql/src/backend/utils/adt (formatting.c)
Date
Msg-id 200006090318.e593IZC44842@hub.org
Whole thread Raw
List pgsql-committers
  Date: Thursday, June  8, 2000 @ 23:18:34
Author: momjian

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/utils/adt
     from hub.org:/home/projects/pgsql/tmp/cvs-serv44818/pgsql/src/backend/utils/adt

Modified Files:
    formatting.c

-----------------------------  Log Message  -----------------------------

The enclosed patch changes the behaviour of the "ordinal" ('TH') format for
to_char.  I don't know about the rest of the world, but the "standard" in
Australia is the following:

        1st, 2nd, 3rd, 4th - 9th
        10th - 19th
        21st, 22nd, 23rd, 24th - 29th (similarly for 30s - 90s)
        110th - 119th (and for all "teens")
        121st, 122nd, 123rd, 124th - 129th

I think you see the trend.  The current code works fine except that it
produces:

        111st, 112nd, 113rd, 114th - 119th
        211st, 212nd, 213rd, 214th - 219th ... and so on.

Without knowing anything about what's supported (and what isn't) in the usual
I18N libraries, should this type of behaviour be defined within the locales?

Daniel Baldoni


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql/src/backend/optimizer/plan (planner.c)
Next
From: Bruce Momjian - CVS
Date:
Subject: pgsql/src/test/regress/expected (inherit.out)