Thanks for the replies, I'm using postgres since 8.3 and didn't notice at
the time of 9.0 release the change in the syntax, as the old syntax still
works, every time I read the current documentation I didn't notice that I
was using it wrong.
I agree with Tom Lane about leaving it alone.
Another q
Kevin Grittner writes:
> It's not really a question of whether we should go back to
> documenting the deprecated syntax, but whether (and when) support
> for it should finally be ripped out. It was last documented in 8.4.
We still document, and support, not only the pre-9.0 COPY syntax but
also
On Fri, Apr 29, 2016 at 10:31 AM, Andrei M. Eichler
wrote:
> Following the documentation, I wrote this COPY FROM command:
>
> COPY test_copy FROM '/mnt/disk1/files/test_file.csv' with csv header
> delimiter ';' force_null date_column, date_column2, date_column3,
> date_column4, date_column5 encod
"Andrei M. Eichler" writes:
> Following the documentation, I wrote this COPY FROM command:
> COPY test_copy FROM '/mnt/disk1/files/test_file.csv' with csv header
> delimiter ';' force_null date_column, date_column2, date_column3,
> date_column4, date_column5 encoding 'latin1';
Which part of the
Hi, thanks for the wiki link.
I'm using Postgrees 9.5.2, running on Debian 8.4
I have a csv file with all columns quoted, even null values.
Following the documentation, I wrote this COPY FROM command:
COPY test_copy FROM '/mnt/disk1/files/test_file.csv' with csv header
delimiter ';' force_null
On Thu, Apr 28, 2016 at 11:58 AM, Andrei M. Eichler
wrote:
> when one tries to use it as it is from the docs, one gets the following
> results:
> ERROR: syntax error at or near "force_null"
Works for me.
Please copy/paste the actual command and the actual, complete error message.
https://wiki
Hi everyone,
In the documentation of COPY options, it lists the following options with a
"_" in it's name:
FORCE_QUOTE
FORCE_NOT_NULL
FORCE_NULL
But when one tries to use it as it is from the docs, one gets the following
results:
ERROR: syntax error at or near "force_null"
Shouldn't it be with
