| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: to_date_valid() |
| Date: | 2016-07-05 04:05:48 |
| Message-ID: | CAFj8pRCrKH0jwBoPTr=zXG7qoUX61BeuFCsTe-csfDhgMUyz6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-07-05 2:39 GMT+02:00 Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>:
> 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?
I have not - so third option looks best for me - it can be long name
"only_correct_date", "only_valid_date", "only_valid_date_on_input" ...
Pavel
>
>
> --
> Andreas 'ads' Scherbaum
> German PostgreSQL User Group
> European PostgreSQL User Group - Board of Directors
> Volunteer Regional Contact, Germany - PostgreSQL Project
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-07-05 04:44:08 | Re: [CF2016-9] Allow spaces in working path on tap-tests |
| Previous Message | Pavel Stehule | 2016-07-05 04:03:35 | Re: to_date_valid() |