From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
---|---|
To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Guillaume Lelarge" <guillaume(at)lelarge(dot)info>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [GENERAL] ISO week dates |
Date: | 2007-02-14 19:26:38 |
Message-ID: | 37ed240d0702141126n27bdedfcr91821aded533e507@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
On 2/15/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > Peter Eisentraut wrote:
> > >> I don't think Oracle even has that. But personally I'd like to see
> > >> errors for invalid pattern combinations.
> >
> > > What do we do with other invalid pattern combinations in to_char() now?
> >
> > Mostly, we return bogus results :-(. The formatting.c code in general
> > doesn't seem very robust.
>
> Yep, seems every release I am in there cleaning up some mistake repeated
> multiple times in the code. It needs a good cleaning.
I'm happy to volunteer to do something about the invalid field
combinations, but I suspect an overhaul of formatting.c is more than I
can currently chew. I figure it would be a bit misguided of me to put
together a patch for invalid field combinations if somebody is about
to do a rewrite of much of the code?
From | Date | Subject | |
---|---|---|---|
Next Message | Ted Byers | 2007-02-14 19:40:18 | Re: backup database by cloning itself |
Previous Message | Mason Hale | 2007-02-14 19:19:32 | Best practice for 8.1.5 -> 8.2 migration - with big database? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-02-14 20:03:37 | Re: [GENERAL] ISO week dates |
Previous Message | Bruce Momjian | 2007-02-14 18:58:13 | Re: [GENERAL] ISO week dates |