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>, "Alex Hunsaker" <badalex(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Meridiem markers (was: [BUGS] Incorrect "invalid AM/PM string" error from to_timestamp) |
Date: | 2009-01-08 03:32:09 |
Message-ID: | 37ed240d0901071932u16d7d3dl7623b0768379cdfb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 8, 2009 at 2:20 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> OK, what is the TODO? It is more than AM/PM, right?
>
I see it happening in two stages.
Stage 1 is updating the AM/PM parse code to use the seq_search
technique, which may involve some minor refactoring around seq_search
itself. This will get us the relaxed validation rules I was talking
about before (i.e., "am" is an acceptable spelling for "AM" and vice
versa).
Stage 2 is improving the error message reporting for all the bits that
use seq_search.
So I would probably make two TODOs, descriptions could be like:
* Relax validation for AM/PM markers in to_timestamp() by using seq_search
* Make to_timestamp() error messages more specific, and display the
actual value which caused the error.
Cheers,
BJ
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-08 03:38:51 | Re: Null row vs. row of nulls in plpgsql |
Previous Message | Bruce Momjian | 2009-01-08 03:30:55 | Re: Common Table Expressions applied; some issues remain |