Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 3E71C475FDA for ; Wed, 13 Nov 2002 20:44:27 -0500 (EST) Received: from sccmmhc01.mchsi.com (sccmmhc01.mchsi.com [204.127.203.183]) by postgresql.org (Postfix) with ESMTP id B4FEC475EF7 for ; Wed, 13 Nov 2002 20:44:26 -0500 (EST) Received: from perdue.net ([12.216.72.93]) by sccmmhc01.mchsi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20021114014428.COVP23765.sccmmhc01.mchsi.com@perdue.net> for ; Thu, 14 Nov 2002 01:44:28 +0000 Message-ID: <3DD2FF93.6060706@perdue.net> Date: Wed, 13 Nov 2002 19:42:43 -0600 From: Tim Perdue User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Old "Feature" - Copy table ignores column defaults Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/217 X-Sequence-Number: 10359 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.php http://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