Date: Fri, 12 Jun 2020 17:28:19 -0400
From: Bruce Momjian <bruce@momjian.us>
To: ehansmair@prompt-software.de, pgsql-docs@lists.postgresql.org
Subject: Re: Documentation  9.8. Data Type Formatting Functions:  missing
 behaviour on invalid input at to_date()
Message-ID: <20200612212819.GA6813@momjian.us>
References: <159135581922.7031.8149548798892105892@wrigleys.postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <159135581922.7031.8149548798892105892@wrigleys.postgresql.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Fri, Jun  5, 2020 at 11:16:59AM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/12/functions-formatting.html
> Description:
> 
> For the formatting functions, which convert between a string and a type like
> date, timestamp or number, there should be a description about the behaviour
> of i.e. to_date(input, mask) in case of invalid, not convertable input.
> 
> I expected a return value of NULL and got a execution error.

Well, the value isn't "unknown", it is invalid, so an error seems
appropriate.  I don't remember anyone complaining the expected a NULL
return.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee