From: | Rich Pixley <rich(dot)pixley(at)hayden(dot)ai> |
---|---|
To: | Samed YILDIRIM <samed(at)reddoc(dot)net> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: csv vs json? |
Date: | 2023-01-09 23:33:01 |
Message-ID: | fe216922-8ab8-3746-9632-3e9f4c9502cc@hayden.ai |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
No error message.
And there was no quoting. That's the bug.
On 1/9/23 3:55 PM, Samed YILDIRIM wrote:
> Hi Rich,
>
> It is hard to say what the problem is you encountered and offer any
> solution. Can you share the error message you got and example lines
> from your csv file?
>
> I only can recommend you to check the document on the link below. CSV
> format of file might not match with default settings of PostgreSQL.
> You can adjust via parameters, such as delimiter, quote, and escape.
>
> https://www.postgresql.org/docs/current/sql-copy.html
>
> Best regards.
> Samed YILDIRIM
>
>
> On Wed, 4 Jan 2023 at 19:10, Rich Pixley <rich(dot)pixley(at)hayden(dot)ai> wrote:
>
> I'm downloading a table in csv using pgAdmin. Some tables work just
> fine. Others have JSON fields in the table and these aren't. What I
> get instead is a string with multiple unquoted double quotes that
> are,
> correctly I think, complained about by my csv reader.
>
> Is there a way to get these quoted properly? Am I doing something
> stupid? Is this a bug?
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2023-01-09 23:58:09 | Re: csv vs json? |
Previous Message | Samed YILDIRIM | 2023-01-09 22:59:22 | Re: MSSQL to PostgreSQL Migration |