From: Wim Bertels <wim.bertels@ucll.be>
To: shammat@gmx.net <shammat@gmx.net>
To: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: nested xml/json to table
Date: Fri, 17 Mar 2023 11:04:42 +0000
Message-ID: <0d59af8d8b855c8f97796e611280b993ee261f7f.camel@ucll.be> (raw)
In-Reply-To: <90741398-62ca-3bd5-79d0-c0f6a2eef4cf@gmx.net>
References: <05b3f3beccba4ce16d2a4ad411085ae5c46e2e82.camel@ucll.be>
<90741398-62ca-3bd5-79d0-c0f6a2eef4cf@gmx.net>
Thomas Kellerer schreef op vr 17-03-2023 om 11:21 [+0100]:
> Wim Bertels schrieb am 17.03.2023 um 11:05:
> > what would be the general idea: "easily" convert an hierarchical
> > structure like json or xml to a table; for example creating columns
> > by
> > appending the key-names when going doing down the three, using null
> > for
> > empty values, adding more columns as needed by the given structure.
> > (1-way operation)
>
>
> You can't have a function that returns a different set of columns
> each time you call it
> (without specifying the output columns - which you don't want).
Hello Thomas,
thanks for the feedback,
i was wondering in the likes of existing built-in functions or
extensions (not CREATE FUNCTION)
mvg,
Wim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: wim.bertels@ucll.be, shammat@gmx.net
Subject: Re: nested xml/json to table
In-Reply-To: <0d59af8d8b855c8f97796e611280b993ee261f7f.camel@ucll.be>
References: <05b3f3beccba4ce16d2a4ad411085ae5c46e2e82.camel@ucll.be> <90741398-62ca-3bd5-79d0-c0f6a2eef4cf@gmx.net> <0d59af8d8b855c8f97796e611280b993ee261f7f.camel@ucll.be>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox