From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | rainer(dot)steinmueller(at)kit(dot)edu |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14449: inconsistency in behaviour of json/jsonb returning functions for sql NULL and json NULL values |
Date: | 2016-12-05 18:30:39 |
Message-ID: | CAKFQuwYEOCzZfF-SfrrmdVpJcGFtZKkz_vtiv0GG3hk=kEWGcQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Dec 5, 2016 at 10:53 AM, <rainer(dot)steinmueller(at)kit(dot)edu> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14449
> Logged by: Rainer Steinmüller
> Email address: rainer(dot)steinmueller(at)kit(dot)edu
> PostgreSQL version: 9.6.1
> Operating system: Debian 3.16.36-1+deb8u2 x86_64 GNU/Linux
> Description:
>
> # all the following sql statements are tested with psql.
> # try to cast or to convert a sql NULL value to json/jsonb null does not
> generate the desired result:
>
> net=> select to_jsonb(null::text);
> to_jsonb
> ----------
>
> (1 row)
>
Previous discussion on -hackers on this topic.
The general conclusion is that the benefit of making this consistent
outweighs the effort to define that consistency and introduce a breakage in
compatibility.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-12-05 18:38:37 | Re: BUG #14446: make_date with negative year |
Previous Message | Tom Lane | 2016-12-05 18:27:09 | Re: BUG #14448: create table as values - type check skipped |