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

Gregory Stark (as CFM) <stark.cfm@gmail.com>

From: "Gregory Stark (as CFM)" <stark.cfm@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Vik Fearing <vik@postgresfriends.org>, Corey Huinker <corey.huinker@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2023-03-28T18:52:50Z

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 Tue, 3 Jan 2023 at 14:16, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Vik Fearing <vik@postgresfriends.org> writes:
>
> > I don't think we should add that syntax until I do get it through the
> > committee, just in case they change something.
>
> Agreed.  So this is something we won't be able to put into v16;
> it'll have to wait till there's something solid from the committee.

I guess I'll mark this Rejected in the CF then. Who knows when the SQL
committee will look at this...

-- 
Gregory Stark
As Commitfest Manager