X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [64.117.224.193])
	by svr1.postgresql.org (Postfix) with ESMTP id DD22730DE16
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 23 Jun 2003 18:17:19 +0000 (GMT)
Received: from svr1.postgresql.org ([64.117.224.193])
	by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new,
	port 10024) with ESMTP id 26897-03
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 23 Jun 2003 15:17:09 -0300 (ADT)
Received: from saphir (dsl-082-082-095-106.arcor-ip.net [82.82.95.106])
	by svr1.postgresql.org (Postfix) with ESMTP id 45F7D30DF06
	for <pgsql-sql@postgresql.org>; Mon, 23 Jun 2003 15:17:09 -0300 (ADT)
Received: by saphir (Postfix, from userid 1000)
	id A9A3213105E; Mon, 23 Jun 2003 20:16:55 +0200 (CEST)
Subject: Re: multi-table unique index
From: Markus Bertheau <twanger@bluetwanger.de>
To: Michael A Nachbaur <mike@nachbaur.com>
Cc: PGSQL-SQL <pgsql-sql@postgresql.org>
In-Reply-To: <200306231032.56257.mike@nachbaur.com>
References: <1056376700.2037.2.camel@fluor>
	<200306231032.56257.mike@nachbaur.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <1056392214.3405.0.camel@saphir>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.0 
Date: 23 Jun 2003 20:16:55 +0200
X-Archive-Number: 200306/271
X-Sequence-Number: 14029

=D0=92 =D0=9F=D0=BD=D0=B4, 23.06.2003, =D0=B2 19:32, Michael A Nachbaur =D0=
=BF=D0=B8=D1=88=D0=B5=D1=82:
> Instead of using the "serial" datatype, you can set it to "int4 PRIMARY K=
EY=20
> DEFAULT nextval(foo_type_id_seq)" and you can manually create the sequenc=
e=20
> "foo_type_id_seq".
>=20
> This way all the tables share the same sequence.

Yeah, but I want to force this behaviour. so that it cannot happen by
accident when you insert records without relying on the sequence.

--=20
Markus Bertheau.
Berlin, Berlin.
Germany.