From: Tim Perdue <tim@perdue.net>
To: pgsql-sql@postgresql.org
Subject: Old "Feature" - Copy table ignores column defaults
Date: Wed, 13 Nov 2002 19:42:43 -0600
Message-ID: <3DD2FF93.6060706@perdue.net> (raw)
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? Right now, it is
substituting 0 for a null column, instead of -99 as I wished, and here I
was complaining that it was the national weather service's bug.
Re: [HACKERS] Bug or feature? COPY ignores column defaults
http://archives.postgresql.org/pgsql-hackers/1999-01/msg00667.phphttp://archives.postgresql.org/pgsql-hackers/1999-01/msg00650.php
Alas, I will have to run perl regex on this awful weather data to make
it work right.
Tim
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: tim@perdue.net
Subject: Re: Old "Feature" - Copy table ignores column defaults
In-Reply-To: <3DD2FF93.6060706@perdue.net>
* 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