Re: remaining sql/json patches
От | Amit Langote |
---|---|
Тема | Re: remaining sql/json patches |
Дата | |
Msg-id | CA+HiwqHx0kAe74hXY-M3GVqZAmZWx+GuAksjcG4iK-ZHoaeBLg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: remaining sql/json patches (Amit Langote <amitlangote09@gmail.com>) |
Ответы |
Re: remaining sql/json patches
Re: remaining sql/json patches |
Список | pgsql-hackers |
On Wed, Mar 27, 2024 at 1:34 PM Amit Langote <amitlangote09@gmail.com> wrote: > On Wed, Mar 27, 2024 at 12:42 PM jian he <jian.universality@gmail.com> wrote: > > hi. > > I don't fully understand all the code in json_table patch. > > maybe we can split it into several patches, > > I'm working on exactly that atm. > > > like: > > * no nested json_table_column. > > * nested json_table_column, with PLAN DEFAULT > > * nested json_table_column, with PLAN ( json_table_plan ) > > Yes, I think it will end up something like this. I'll try to post the > breakdown tomorrow. Here's patch 1 for the time being that implements barebones JSON_TABLE(), that is, without NESTED paths/columns and PLAN clause. I've tried to shape the interfaces so that those features can be added in future commits without significant rewrite of the code that implements barebones JSON_TABLE() functionality. I'll know whether that's really the case when I rebase the full patch over it. I'm still reading and polishing it and would be happy to get feedback and testing. -- Thanks, Amit Langote
Вложения
В списке pgsql-hackers по дате отправления: