Re: Bypassing NULL elements in row_to_json function

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Michael Nolan <htfoot(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Bypassing NULL elements in row_to_json function
Date: 2016-04-10 07:30:26
Message-ID: CAKFQuwbz-Rm=gxx5_s94H13yNohyPmUa2KVf3k5-3oKQUL1sBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Apr 9, 2016 at 9:48 PM, Michael Nolan <htfoot(at)gmail(dot)com> wrote:

>
> 2nd Followup: It turns out that loading a table from a JSON string is
> more complicated than going from a table to JSON, perhaps for good reason.
> There does not appear to be a direct inverse to the row_to_json() function,
> but it wasn't difficult for me to write a PHP program that takes the JSON
> file I created the other day and converts it back to a series of inserts,
> recreating the original table.
>
> Of course this simple program does NO validation (not that this file
> needed any), so if the JSON string is not well-formed for any of a number
> of reasons, or if it is not properly mapped to the table into which the
> inserts are made, an insert could fail or result in incorrect data.
> --
> Mike Nolan
>

​See: http://www.postgresql.org/docs/9.5/interactive/functions-json.html

​json_populate_record(base anyelement, from_json json)
json_populate_recordset(base anyelement, from_json json)

Exists in 9.3 too...though if you are going heavy json I'd suggest doing
whatever you can to keep up with the recent releases.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Venkata Balaji N 2016-04-10 08:05:51 Re: Shipping big WAL archives to hot standby
Previous Message Durumdara 2016-04-10 07:07:34 Re: Really unique session ID - PID + connection timestamp?