X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9B3E1D1B16A for ; Thu, 22 Jul 2004 09:44:58 -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 07104-06 for ; Thu, 22 Jul 2004 12:44:58 +0000 (GMT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id B257CD1B377 for ; Thu, 22 Jul 2004 09:44:50 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id 5D0BC55EAE; Thu, 22 Jul 2004 14:44:59 +0200 (CEST) Received: from www.credativ.de (pD95012DF.dip0.t-ipconnect.de [217.80.18.223]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by curie.credativ.org (Postfix) with ESMTP id E728C55BC8; Thu, 22 Jul 2004 14:44:58 +0200 (CEST) Received: from bell.credativ.de (bell.credativ.de [172.26.14.16]) by www.credativ.de (Postfix) with ESMTP id BE54D1C0004; Thu, 22 Jul 2004 14:44:57 +0200 (CEST) From: Peter Eisentraut To: Michal Dobaczewski Subject: Re: libpq: usage of PQoidValue to obtain serial primary key after insert Date: Thu, 22 Jul 2004 14:44:56 +0200 User-Agent: KMail/1.6.2 Cc: pgsql-interfaces@postgresql.org References: <40FFA197.9080106@cc.com.pl> In-Reply-To: <40FFA197.9080106@cc.com.pl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407221444.56693.peter_e@gmx.net> X-Virus-Scanned: by AMaViS at credativ.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_NJABL, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/36 X-Sequence-Number: 5042 Am Donnerstag, 22. Juli 2004 13:14 schrieb Michal Dobaczewski: > Browsing the general list I've just read a post claiming that oid are > not guaranteed to be unique in the table. This is also stated in the > documentation - which seems to have escaped me this far. So I assume the > approach presented above is flawed. > > I would like to ask what is a most elegant way to deal with such issues? Create a unique constraint on the oid column. -- Peter Eisentraut http://developer.postgresql.org/~petere/