| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First draft of PG 17 release notes |
| Date: | 2024-05-16 08:29:38 |
| Message-ID: | CACJufxE0HY19F8Oo-wb-+i4bKDamiaL_aUV8qB69_8mwoScZow@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 9, 2024 at 12:04 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> I have committed the first draft of the PG 17 release notes; you can
> see the results here:
>
> https://momjian.us/pgsql_docs/release-17.html
>
>> Add jsonpath methods to convert JSON values to different data types (Jeevan Chalke)
>> The jsonpath methods are .bigint(), .boolean(), .date(), .decimal([precision [, scale]]), .integer(), .number(), .string(), .time(), .time_tz(), .timestamp(), and .timestamp_tz().
I think it's slightly incorrect.
for example:
select jsonb_path_query('"2023-08-15"', '$.date()');
I think it does is trying to validate json value "2023-08-15" can be a
date value, if so, print json string out, else error out.
"convert JSON values to different data types"
meaning that we are converting json values to another data type, date?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2024-05-16 08:57:10 | Re: Postgres and --config-file option |
| Previous Message | Andrei Lepikhov | 2024-05-16 07:47:01 | Re: POC: GROUP BY optimization |