Re: PostgreSQL 17 Beta 1 release announcement draft

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>
Subject: Re: PostgreSQL 17 Beta 1 release announcement draft
Date: 2024-05-20 16:44:23
Message-ID: a68559e1-236f-4091-8f58-b9caa2d96e05@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/20/24 8:31 AM, jian he wrote:

> release note (https://momjian.us/pgsql_docs/release-17.html)
> is
> "Add jsonpath methods to convert JSON values to other JSON data types
> (Jeevan Chalke)"
>
>
>>> Additionally, PostgreSQL 17 adds more functionality to its `jsonpath` implementation, including the ability to convert JSON values to different data types.
> so, I am not sure this is 100% correct.
>
> Maybe we can rephrase it like:
>
>>> Additionally, PostgreSQL 17 adds more functionality to its `jsonpath` implementation, including the ability to convert JSON values to other JSON data types.

The release note goes on to state:

==
The jsonpath methods are .bigint(), .boolean(), .date(),
.decimal([precision [, scale]]), .integer(), .number(), .string(),
.time(), .time_tz(), .timestamp(), and .timestamp_tz().
==

And reviewing the docs[1], these are converted to a PostgreSQL native
types, and not JSON types (additionally a bunch of those are not JSON
types).

Jeevan: can you please confirm that this work converts into the
PostgreSQL native types?

Thanks,

Jonathan

[1] https://www.postgresql.org/docs/devel/functions-json.html

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2024-05-20 16:45:39 Re: PostgreSQL 17 Beta 1 release announcement draft
Previous Message Tom Lane 2024-05-20 16:44:14 Re: Reading timestamp values from Datums gives garbage values