| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Alternative to \copy in psql modelled after \g |
| Date: | 2018-11-09 17:23:10 |
| Message-ID: | 7b3b6730-03eb-49fd-9313-0f3ca976f19b@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 503 사설 토토 사이트 |
David G. Johnston wrote:
> POLA, for me at least, would be for \g [filename] to do exactly what
> you are describing with the \copyto feature.
I admit that if we could improve \g to handle COPY, it would be more
elegant than the current proposal adding two meta-commands.
But the copy-workflow and non-copy-workflow are different, and in
order to know which one to start, \g would need to analyze the query
to determine whether it's a COPY FROM, COPY TO or something else.
psql parses queries syntactically, but not semantically AFAIK, and I
suspect we don't want to start doing that, as it breaks a separation
of concerns.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2018-11-09 17:23:42 | Re: [HACKERS] Surjective functional indexes |
| Previous Message | Alvaro Herrera | 2018-11-09 17:07:12 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |