On Jan 9, 2015, at 11:37 AM, Andrew Dunstan and...@dunslane.net wrote:
On 01/08/2015 08:42 PM, Aaron Botsis wrote:
On Jan 8, 2015, at 3:44 PM, Andrew Dunstan and...@dunslane.net wrote:
On 01/08/2015 03:05 PM, Aaron Botsis wrote:
It's also unnecessary. CSV format, while
On Jan 8, 2015, at 3:44 PM, Andrew Dunstan and...@dunslane.net wrote:
On 01/08/2015 03:05 PM, Aaron Botsis wrote:
It's also unnecessary. CSV format, while not designed for this, is
nevertheless sufficiently flexible to allow successful import of json data
meeting certain criteria
On Jan 7, 2015, at 2:45 PM, Andrew Dunstan and...@dunslane.net wrote:
On 01/07/2015 08:25 AM, Aaron Botsis wrote:
Hi folks, I was having a problem importing json data with COPY. Lots of
things export data nicely as one json blob per line. This is excellent for
directly importing
o Olarte fola...@peoplecall.comDate: January 6, 2015 at 1:52:28 PM ESTSubject: Re: [BUGS] BUG #12320: json parsing with embedded double quotesTo: Aaron Botsis aa...@bt-r.comCc: postg...@bt-r.com, "pgsql-b...@postgresql.org" pgsql-b...@postgresql.orgHi Aaron:On Tue, Jan 6, 2015 at 7:06 PM, Aaron
Ack. Original had a bug. Let’s try again.
escape-without-csv-v2.patch
Description: Binary data
On Jan 7, 2015, at 8:25 AM, Aaron Botsis aa...@bt-r.com wrote:Hi folks, I was having a problem importing json data with COPY. Lots of things export data nicely as one json blob per line
