From: | matti(dot)hameister(at)technologygroup(dot)de |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #10728: json_to_recordset with nested json objects NULLs columns |
Date: | 2014-06-22 15:34:09 |
Message-ID: | 20140622153409.2618.90346@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
The following bug has been logged on the website:
Bug reference: 10728
Logged by: Matti Hameister
Email address: matti(dot)hameister(at)technologygroup(dot)de
PostgreSQL version: 9.4beta1
Operating system: Linux
Description:
This query:
--
SELECT X.* FROM
json_to_record(
'
{"a":2,"c":3,"b":{"z":4}, "d":6}
',true
) AS X(a int, b json, c int, d int);
--
returns as expected
a: 2
b: {"z":4}
c: 3
d: 6
Now I changed the query a bit (using recordset):
--
SELECT X.* FROM
json_to_recordset(
'[
{"a":2,"c":3,"b":{"z":4}, "d":6}
]
',true
) AS X(a int, b json, c int, d int);
--
the result is surprising:
a: NULL
b: {"z":4}
c: NULL
d: 6
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-06-23 05:13:28 | Re: BUG #10728: json_to_recordset with nested json objects NULLs columns |
Previous Message | wildfox81 | 2014-06-22 12:37:58 | BUG #10726: database gets to an older backup out of nowhere!!! |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-06-22 15:58:04 | Re: tab completion for setting search_path |
Previous Message | Andres Freund | 2014-06-22 15:30:35 | Re: idle_in_transaction_timeout |