X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 37845D9933 for ; Tue, 27 Sep 2005 12:33:19 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 39915-04 for ; Tue, 27 Sep 2005 15:33:17 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 5F35DD9921 for ; Tue, 27 Sep 2005 12:33:16 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 27 Sep 2005 10:33:14 -0500 Subject: Re: Why doesn't the SERIAL data type automatically have a From: Scott Marlowe To: Tom Lane Cc: fmiddleton@verizon.net, pgsql-sql@postgresql.org In-Reply-To: <5899.1127782998@sss.pgh.pa.us> References: <4338961E.20100@verizon.net> <5899.1127782998@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1127835194.29347.12.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 27 Sep 2005 10:33:14 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 required=5 tests=[AWL=0.007] X-Spam-Level: X-Archive-Number: 200509/271 X-Sequence-Number: 22818 On Mon, 2005-09-26 at 20:03, Tom Lane wrote: > Ferindo Middleton Jr writes: > > Is there some reason why the SERIAL data type doesn't automatically have > > a UNIQUE CONSTRAINT. > > It used to, and then we decoupled it. I don't think "I have no use for > one without the other" translates to an argument that no one has a use > for it ... I have to admit, right after the change was made, I was of the opinion that no one would ever need that. Then, a few months later, it was exactly what I needed for some project... :)