public inbox for [email protected]  
help / color / mirror / Atom feed
From: Vik Fearing <[email protected]>
To: Corey Huinker <[email protected]>
To: jian he <[email protected]>
Cc: Amul Sul <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Kirill Reshke <[email protected]>
Cc: Isaac Morland <[email protected]>
Cc: [email protected]
Subject: Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions
Date: Thu, 2 Apr 2026 18:03:28 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADkLM=cXsprF2GvcmqOG+ME_N2iyHNr_--xW-6ZaKd32yF_NzA@mail.gmail.com>
References: <CADkLM=fv1JfY4Ufa-jcwwNbjQixNViskQ8jZu3Tz_p656i_4hQ@mail.gmail.com>
	<CADkLM=cmv_bmxBe8KmZd6rEgiqSdoDfHnJa63u7rdRuAsqOwDA@mail.gmail.com>
	<CACJufxGbw9iNT8QVm4QD9cPFKnDnvDBQp7AGxkoqDa-JjzVXmg@mail.gmail.com>
	<CACJufxFkLLuX1VJ-J3fppCr37PHtxkvwyd_e4zNd+VYK0v0gnQ@mail.gmail.com>
	<[email protected]>
	<CACJufxHx-UfprE6P4_ZB_cOYktHd4pLMNx=jWJFOGGGFj2YZWQ@mail.gmail.com>
	<CACJufxH_1EtEBMb0JvxaM3Gmnt33HYrS37m5eYjJ_OfBkMVFJg@mail.gmail.com>
	<CACJufxHGox47X4zNtVeNw7H=SZ7ATAAD5SEYpvxa2o5mPV0XCA@mail.gmail.com>
	<[email protected]>
	<CAAJ_b959dfJsorK+_vPdVa8F3QYPdOnb-HzJY8oQQR91N9Tq2A@mail.gmail.com>
	<CACJufxFOQkmH9KeQNTD0qASbL3i03cLeoyVZdcZ8Fm0rk6eJ5Q@mail.gmail.com>
	<CACJufxEUr33CoQMsZdEehNU7wj_QOiyk8VW=W+aB03PF2J_qKQ@mail.gmail.com>
	<CACJufxGx_XDHq1btNj=ZrBjwd0skeWFJQLMGqSR-pHw-kuYRnQ@mail.gmail.com>
	<CADkLM=cXsprF2GvcmqOG+ME_N2iyHNr_--xW-6ZaKd32yF_NzA@mail.gmail.com>


On 31/03/2026 22:02, Corey Huinker wrote:
>
>
> On Tue, Mar 31, 2026 at 10:48 AM jian he <[email protected]> 
> wrote:
>
>     Hi.
>     I've incorporated the changes you sent me off-list.
>     The attached v1 no-cfbot is your proposed change.
>     I also did some minor comments adjustments.
>
>
> The remaining patches continue to work for me. I hope we can get all 
> of this into 19, but if we can't I think it would be ok to limit 
> src/dest type combinations to those that can be handled by 
> CoerceViaIO, at least for 19. I think the vast majority of the usage 
> of this function will be mass ETLs where data is first loaded into a 
> table of all text.


Did you see on Discord that I am submitting a bug fix for this paper? I 
originally took the syntax from json but it special-cases NULL and can't 
handle <empty specification>, so I want to remove `NULL ON CONVERSION 
ERROR` and switch the DEFAULT clause to <implicitly typed value 
specification>.


I am attaching it here in case you missed it.

-- 

Vik Fearing


Attachments:

  [application/pdf] bma014-cast-error-default--draft-01.pdf (51.6K, 3-bma014-cast-error-default--draft-01.pdf)
  download

view thread (67+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox