Received: from kss.net.au ([203.41.122.41]) by hub.org (8.10.1/8.10.1) with ESMTP id e6K7Mih90811 for ; Thu, 20 Jul 2000 03:22:44 -0400 (EDT) Received: from kss.net.au (coco [10.10.1.9]) by kss.net.au (8.8.7/8.8.7) with ESMTP id RAA15963 for ; Thu, 20 Jul 2000 17:24:57 +1000 Message-ID: <3976A9A6.55E6BE2E@kss.net.au> Date: Thu, 20 Jul 2000 17:26:30 +1000 From: Carolyn Lu Wong Organization: Kwiker Software Solutions X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "pgsql-sql@postgresql.org" Subject: primary key question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200007/189 create table aaa( field1 .... not null, field2 ...., ...., primary key (field1, field2) ); Based on the above table definition, field2 allows null values. But after the table created based on the above script, field2 becomes not null. The only conclusion I come up with is setting the field as part of the primary key, PostgreSQL automatically sets the field to not null. Or is it something else? Is this a feature or bug?