Re: SQL/JSON: JSON_TABLE
От | Erik Rijkers |
---|---|
Тема | Re: SQL/JSON: JSON_TABLE |
Дата | |
Msg-id | e1cb24f2-7c11-8916-5b62-f029fb3225b1@xs4all.nl обсуждение исходный текст |
Ответ на | Re: SQL/JSON: JSON_TABLE (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>) |
Ответы |
Re: SQL/JSON: JSON_TABLE
|
Список | pgsql-hackers |
On 5/18/21 9:23 PM, Andrew Dunstan wrote: > > On 5/8/21 2:23 PM, Andrew Dunstan wrote: >> On 4/12/21 11:34 AM, Erik Rijkers wrote: >>>> On 2021.03.27. 02:12 Nikita Glukhov <n.gluhov@postgrespro.ru> wrote: >>>> Attached 47th version of the patches. >>> We're past feature freeze for 14 and alas, JSON_TABLE has not made it. >>> >>> I have tested quite a bit with it and because I didn't find any trouble with functionality or speed, I wanted to at leastmention that here once. >>> >>> I looked at v47, these files >>>> [0001-SQL-JSON-functions-v47.patch] >>>> [0002-JSON_TABLE-v47.patch] >>>> [0003-JSON_TABLE-PLAN-DEFAULT-clause-v47.patch] >>>> [0004-JSON_TABLE-PLAN-clause-v47.patch] >>>> [manual_addition_fixed.patch] # for this see [1], [2] >>> (v47 doesn't apply anymore, as cfbot shows, but instances can still be built on top of 6131ffc43ff from 30 march2021) >>> >>> I hope it will fare better next round, version 15. >> >> Me too. Here's a set that should remove the bitrot. > > Rebased for removal of serial schedule Can one of you please add or integrate this patch to the JSON_TABLE changes? It contains the fix for a bug that I reported earlier (on 2021-03-30 see [1]). Nikita did diagnose this fix but today I noticed it was still not included in the latest version, v49. Thanks, Erik Rijkers [1] https://www.postgresql.org/message-id/2101814418.20240.1617123418368%40webmailclassic.xs4all.nl > > -- > Andrew Dunstan > EDB: https://www.enterprisedb.com >
Вложения
В списке pgsql-hackers по дате отправления: