Date: Mon, 26 Sep 2005 20:45:18 -0400
From: Ferindo Middleton Jr <fmiddleton@verizon.net>
Subject: Why doesn't the SERIAL data type automatically have a UNIQUE
	CONSTRAINT
To: pgsql-sql@postgresql.org
Reply-To: fmiddleton@verizon.net
Message-id: <4338961E.20100@verizon.net>
Organization: Sleek Collar
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
User-Agent: Thunderbird 1.4 (Windows/20050908)

Is there some reason why the SERIAL data type doesn't automatically have 
a UNIQUE CONSTRAINT. It seems that the main reason for using it is so 
that the value for this field keeps changing automatically and is never 
null so any one record can be identified using it- So why not imply that 
it is always be UNIQUE anyway. I mean, if you were to force another 
value on a SERIAL field that already had that same value, the would 
through the sequence tracking the the fields current value off any way, 
so it just makes sense to me to not let a serial field be duplicated. 
Let's take a poll. Is there anyone out there who actually uses the 
SERIAL data type who would not want it to be UNIQUE?

Ferindo