From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tim Perdue <tim@perdue.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: Old "Feature" - Copy table ignores column defaults
Date: Wed, 13 Nov 2002 23:37:49 -0500
Message-ID: <27212.1037248669@sss.pgh.pa.us> (raw)
In-Reply-To: <3DD2FF93.6060706@perdue.net>
References: <3DD2FF93.6060706@perdue.net>
Tim Perdue <tim@perdue.net> writes:
> I see there are a handful of reports of this, but it does seem broken to
> me. If I am copying a table and a column is blank, surely it makes sense
> to substitute the column default from the table?
There is no such concept as "blank" in SQL.
7.3 does have the ability to COPY a subset of a column's tables and
insert default values for the omitted columns. But if a column is
provided in the input, there is no clean way to decide that a particular
input value ought to be replaced by a default.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, tim@perdue.net
Subject: Re: Old "Feature" - Copy table ignores column defaults
In-Reply-To: <27212.1037248669@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox