Re: COPY WITH CSV FORCE QUOTE *

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY WITH CSV FORCE QUOTE *
Date: 2009-07-16 19:03:27
Message-ID: 4A5F797F.4040508@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew,

> FORCE NOT NULL is in any case a fairly blunt instrument - it doesn't
> work for a column of any type that doesn't accept an empty string as
> valid input, such as numeric types.

Con: this allows COPY to produce output which cannot be reloaded into
PostgreSQL.

Pro: there is a lot of extremely broken external software which expects
"nulls" to be expressed as "". This improves compatiblity with them.

--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-07-16 19:08:25 pg_stat_activity.application_name
Previous Message Bruce Momjian 2009-07-16 18:58:20 Re: [GENERAL] pg_migrator not setting values of sequences?