Re: Bypassing NULL elements in row_to_json function - Mailing list pgsql-general

From Michael Nolan
Subject Re: Bypassing NULL elements in row_to_json function
Date
Msg-id CAOzAquJkczwhT5iV5a-SU54SeVxHXfMUV86jQ8f8F9HArSV70A@mail.gmail.com
Whole thread Raw
In response to Re: Bypassing NULL elements in row_to_json function  (Michael Nolan <htfoot@gmail.com>)
Responses Re: Bypassing NULL elements in row_to_json function
List pgsql-general

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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: max_stack_depth problem though query is substantially smaller
Next
From: Durumdara
Date:
Subject: Re: Really unique session ID - PID + connection timestamp?