pg.ddx.io  pgsql-general@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Davin Shearer <davin@apache.org>
To: Joe Conway <mail@joeconway.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Emitting JSON to file using COPY TO
Date: Mon, 4 Dec 2023 15:06:31 -0500
Message-ID: <5c84b70b-ba18-c45d-dbbe-612fa229b2ce@dunslane.net> (raw)
In-Reply-To: <CALvfUkB2QtG-BXsTwjoLO8ZYUsNFytqjPvZex8stQ0r_qNM7HQ@mail.gmail.com>
References: <CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU=kcg@mail.gmail.com>
	<3853387.1701096982@sss.pgh.pa.us>
	<CAFCRh-_GdiUvjd5z5FfvTfhruOnYqBu163XU47zZE8RNATCJGQ@mail.gmail.com>
	<3a98decf-3fe3-4b49-9b68-fda01338872c@sedlakovi.org>
	<CALvfUkCq3pvkmniWEKZwkbA6hNNvkANF3OamMfhC170RgY+HJg@mail.gmail.com>
	<24e3ee88-ec1e-421b-89ae-8a47ee0d2df1@joeconway.com>
	<b22367ef-6ac1-e1c0-da05-0e760e1b7e29@dunslane.net>
	<CALvfUkD9ZFUU2pe9RMPqdGaKXu5OZi5xzOiPokGhOoPJ56FgAw@mail.gmail.com>
	<7117a356-916c-4cf3-bad8-861490e65dcf@joeconway.com>
	<CALvfUkBKTr9WLAbHQYmwZ7SVp5_VDey1F1uCZtKL4+H1-WvyBw@mail.gmail.com>
	<b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com>
	<9c77b6fa-ee88-b2e6-0fa7-4fc81721da35@dunslane.net>
	<c30fc5da-0348-4e44-b699-804ccbdcfc36@joeconway.com>
	<41dcba92-1075-e5e5-cb99-36711abf6cec@dunslane.net>
	<bcbb2a04-5df3-49f2-b304-28ae8edc5189@joeconway.com>
	<CALvfUkB2QtG-BXsTwjoLO8ZYUsNFytqjPvZex8stQ0r_qNM7HQ@mail.gmail.com>


On 2023-12-04 Mo 13:37, Davin Shearer wrote:
> Looking great!
>
> For testing, in addition to the quotes, include DOS and Unix EOL, \ 
> and /, Byte Order Markers, and mulitbyte characters like UTF-8.
>
> Essentially anything considered textural is fair game to be a value.


Joe already asked you to avoid top-posting on PostgreSQL lists. See 
<http://idallen.com/topposting.html; 
<http://idallen.com/topposting.html>; for an explanation.

We don't process BOMs elsewhere, and probably should not here either. 
They are in fact neither required nor recommended for use with UTF8 
data, AIUI. See a recent discussion on this list on that topic: 
<https://www.postgresql.org/message-id/flat/81ca2b25-6b3a-499a-9a09-2dd21253c2cb%40unitrunker.net;


cheers


andrew


--
Andrew Dunstan
EDB:https://www.enterprisedb.com

view thread (163+ messages)  latest in thread

Message-ID: <5c84b70b-ba18-c45d-dbbe-612fa229b2ce@dunslane.net>
Permalink:  ../5c84b70b-ba18-c45d-dbbe-612fa229b2ce@dunslane.net/
Also on:    postgresql.org/message-id/5c84b70b-ba18-c45d-dbbe-612fa229b2ce@dunslane.net

 · 

reply
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 using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: andrew@dunslane.net, davin@apache.org, mail@joeconway.com, pgsql-hackers@postgresql.org
  Subject: Re: Emitting JSON to file using COPY TO
  In-Reply-To: <5c84b70b-ba18-c45d-dbbe-612fa229b2ce@dunslane.net>

* 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