Re: COPY with default values?

From: Jeff Boes <jboes(at)nexcerpt(dot)com>
To: Postgres-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: COPY with default values?
Date: 2001-05-25 15:10:01
Message-ID: 20010525111001.71a4ebc8.jboes@nexcerpt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On Fri, 25 May 2001 10:33:41 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> COPY does not deal with insertion of default values. Sorry.

This seems odd to me, especially since Pgsql treats

INSERT INTO keywords (key_id, key_text) VALUES (null, 'foo');

differently than

INSERT INTO keywords (key_text) VALUES ('foo');

It's been a while, but I'm pretty sure Oracle will do the same thing for
each of these inserts, namely apply a default value when a null is
detected.

But thanks for the help!

--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt, Inc. jboes(at)nexcerpt(dot)com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Arcady Genkin 2001-05-25 15:51:26 Compilation fails --with-ssl on Solaris 8
Previous Message Peter Kelly 2001-05-25 15:03:46 RE: DATE_PART() BUG? We have an SQL statement that is giving wro ng output.

Browse pgsql-general by date

  From Date Subject
Next Message Farid Hajji 2001-05-25 15:24:18 Re: Trouble with strange OUTER JOIN syntax
Previous Message Sean Chittenden 2001-05-25 14:56:28 Re: Username with a hyphen character (grant failing?)