From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Milorad Krstevski <miloradkrstevski(at)gmail(dot)com> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15206: Can not import CSV into PostgreSQL |
Date: | 2018-05-19 19:05:09 |
Message-ID: | CAKFQuwbhBFN=je58novM82eVWikMDhXj_KG=5_jpxYLu0C5E1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sat, May 19, 2018 at 8:05 AM, Milorad Krstevski <
miloradkrstevski(at)gmail(dot)com> wrote:
> So first I have to create all (for example 50 columns and define them in
> data type) and then import? That is not the case with any other db.
>
>
Cannot speak about others but stock PostgreSQL, yes.
Haven't used it but the following seems relevant if you are looking for a
tool to make life easier:
http://csvkit.readthedocs.io/en/1.0.3/tutorial/3_power_tools.html#csvsql-and-sql2csv-ultimate-power
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2018-05-19 20:57:44 | Re: BUG #15200: Support ANSI OFFSET .. FETCH syntax with bind variables |
Previous Message | Tom Lane | 2018-05-19 16:45:00 | Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT |