Re: to_date_valid() - Mailing list pgsql-hackers

From Andreas 'ads' Scherbaum
Subject Re: to_date_valid()
Date
Msg-id 577B01A9.8080102@wars-nicht.de
Whole thread Raw
In response to Re: to_date_valid()  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: to_date_valid()  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: to_date_valid()  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On 04.07.2016 18:37, Pavel Stehule wrote:
>
> I don't know if the name "strict" is best, but the name "validate" is
> not good too. Current to_date does some validations too.

Obviously not enough, because it allows invalid dates. I'd say that the 
current to_date() merely validates the input format for string parsing, 
and that the date is in range. But there is not much validation on the 
date itself.

So the name can't be "strict" because of the conflict with "NULL" 
handling, and you don't like "valid" - what other options do you offer?

--             Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project



pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: to_date_valid()
Next
From: "David G. Johnston"
Date:
Subject: Re: to_date_valid()