Re: Invalid to_date patterns (was: [PATCHES] [GENERAL] ISO week dates) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Invalid to_date patterns (was: [PATCHES] [GENERAL] ISO week dates)
Date
Msg-id 23634.1184685529@sss.pgh.pa.us
Whole thread Raw
In response to Re: Invalid to_date patterns (was: [PATCHES] [GENERAL] ISO week dates)  ("Brendan Jurd" <direvus@gmail.com>)
Responses Re: Invalid to_date patterns (was: [PATCHES] [GENERAL] ISO week dates)  ("Brendan Jurd" <direvus@gmail.com>)
List pgsql-hackers
"Brendan Jurd" <direvus@gmail.com> writes:
>> * Fix to_date()-related functions to consistently issue errors
>> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php

> I'm now taking another run at this issue.  Here's what I've got in mind.

This is all good but I think that self-inconsistent format strings are
not really the main source of to_date problems.  Most of the complaints
I've seen arise from to_date plowing ahead to deliver a ridiculous
answer when the input data string doesn't match the format.  I'd like to
see the code try a little harder to validate the input data.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Backend memory growing too much
Next
From: Andrew Dunstan
Date:
Subject: Re: write_pipe_chunks patch messes up early error message output