Received: from megazone.bigpanda.com ([63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9VMeNP44897 for ; Wed, 31 Oct 2001 17:40:24 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id AC9F3D5D7; Wed, 31 Oct 2001 14:40:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id A03C85BD8; Wed, 31 Oct 2001 14:40:21 -0800 (PST) Date: Wed, 31 Oct 2001 14:40:21 -0800 (PST) From: Stephan Szabo To: =?ISO-8859-1?Q?St=E9phane_Chomat?= Cc: Subject: Re: Primary key with oid + name : error, which solution ? In-Reply-To: <9F2CCC32-CE4D-11D5-9FB4-003065C28650@mac.com> Message-ID: <20011031143839.P19548-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by postgresql.org id f9VMq2M46919 X-Archive-Number: 200110/434 X-Sequence-Number: 5385 On Wed, 31 Oct 2001, [ISO-8859-1] Stéphane Chomat wrote: > Yes, name is an internal type. The problem is in the type of the table > repertory. If it is not > possible to use this syntaxe, i will take the type char. I just try the > new possibility of postgressql. Yeah. I think the problem is that you'd need an operator class to take two objects of type repertory and sort them because the uniqueness is handled via with the index system.