Re: BUG #15206: Can not import CSV into PostgreSQL - Mailing list pgsql-bugs
From | Milorad Krstevski |
---|---|
Subject | Re: BUG #15206: Can not import CSV into PostgreSQL |
Date | |
Msg-id | CACH_0iovFKHTjfmLWGLJVM8yc=cofmVzdcYsTSjZNZHR_BN6-w@mail.gmail.com Whole thread Raw |
In response to | Re: BUG #15206: Can not import CSV into PostgreSQL ("David G. Johnston" <david.g.johnston@gmail.com>) |
Responses |
Re: BUG #15206: Can not import CSV into PostgreSQL
|
List | pgsql-bugs |
Please find in attach the backup schema.
I really do not know how to export the settings (or what is needed to you). If you could please send me screen of what is needed?
I created all db, schema and table empty with default settings. Nothing is changed or limited. I put postgre user with all privileges everywhere. That's it. Nothing else.
On Sat, May 19, 2018 at 4:31 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:
The definition of the neptune.act table. The pgAdmin docs can walk you through how to go about finding that if you cannot intuit how to navigate the object browser it provides.You need to count how many columns are on that table and compare them to how many are in the csv file. You should find there are fewer in the table which means you need to fix the table. If you find the counts to be the same then it might be something different.DaveOn Sat, May 19, 2018 at 7:25 AM, Milorad Krstevski <miloradkrstevski@gmail.com> wrote:Screenshot of what?I will take now but please point me out.On Sat, May 19, 2018 at 4:24 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:A screenshot would be better for me, dealing with a dump file is too high-maintenance for this kind of question.On Sat, May 19, 2018 at 7:18 AM, Milorad Krstevski <miloradkrstevski@gmail.com> wrote:Is this OK?Please let me know. Thank you.On Sat, May 19, 2018 at 4:14 PM, Milorad Krstevski <miloradkrstevski@gmail.com> wrote:Here is the backup of the whole db.It is empty. The pass is: miki (in case you need it).On Sat, May 19, 2018 at 3:57 PM, Milorad Krstevski <miloradkrstevski@gmail.com> wrote:Respected,Thank you very much for the prompt reply.I am trying to import the following files in new created empty table in postgre db and schema (both are neptun, and the table is act):1. s1.csv - is created manually by me (encoding UTF8 and delimiter ;) - attachment 12. act2017short2.csv - is taken from system (I just put 10 lines here) - attachment 2The error that is shown in the import is below. I go import as CSV - encoding UTF8 with header and delimiter ; - nothing else in the import wizard is changed.1. Attachment 3: Error 12. Attachment 4: Error 2Can you please point me out where is my mistake? Thank you.Respectfully,Milorad K.--On Sat, May 19, 2018 at 2:55 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:Hi2018-05-19 11:09 GMT+02:00 PG Bug reporting form <noreply@postgresql.org>:The following bug has been logged on the website:
Bug reference: 15206
Logged by: Milorad Krstevski
Email address: miloradkrstevski@gmail.com
PostgreSQL version: 10.4
Operating system: Ubuntu 18.04 LTS x64
Description:
Respected,
No matter what I try, I always get the error: ERROR: extra data after last
expected column, and can not import CSV into table in PostgreSQL.
I am using pgAdmin 4.30, Python 3.6.5, Flask 0.12.2.
Can you please point out solution to my problem please?It is not PostgreSQL bug, so pg_general mailing list will be better.PostgreSQL is very strict about CSV format - it looks so some line of CSV doc has more columns than target table.IOW, we cannot help unless you provide both the CSV file and the table definition.David J.
--
--
--
--
Attachment
pgsql-bugs by date: