Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions

Isaac Morland <isaac.morland@gmail.com>

From: Isaac Morland <isaac.morland@gmail.com>

To: Corey Huinker <corey.huinker@gmail.com>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2023-03-28T19:25:05Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Make cast functions to type money error safe
- b36b95640487 19 (unreleased) landed
Make cast function from circle to polygon error safe
- 26f9012beecf 19 (unreleased) landed
Make geometry cast functions error safe
- 45cdaf3665be 19 (unreleased) landed
Make cast functions from jsonb error safe
- 10e4d8aaf46f 19 (unreleased) landed
Make many cast functions error safe
- e2f289e5b9b8 19 (unreleased) landed
Add SQL/JSON query functions
- 6185c9737cf4 17.0 cited
Add soft error handling to some expression nodes
- aaaf9449ec6b 17.0 cited

On Mon, 19 Dec 2022 at 17:57, Corey Huinker <corey.huinker@gmail.com> wrote:

>
> Attached is my work in progress to implement the changes to the CAST()
> function as proposed by Vik Fearing.
>
> CAST(expr AS typename NULL ON ERROR)
>     will use error-safe functions to do the cast of expr, and will return
> NULL if the cast fails.
>
> CAST(expr AS typename DEFAULT expr2 ON ERROR)
>     will use error-safe functions to do the cast of expr, and will return
> expr2 if the cast fails.
>

Is there any difference between NULL and DEFAULT NULL?