Wrong OID for Primary Key and UNIQUE constraints shown in property pane - Mailing list pgadmin-support

From Harald Armin Massa
Subject Wrong OID for Primary Key and UNIQUE constraints shown in property pane
Date
Msg-id 7be3f35d0704040641n1e2ddceax4cf5fee26a387790@mail.gmail.com
Whole thread Raw
Responses Re: Wrong OID for Primary Key and UNIQUE constraints shown in property pane
List pgadmin-support
Hello,<br /><br />I tried to get the definition of unique and primary key constraints via<br /><br />select
pg_get_constraintdef(<oidofconstraint>)<br/><br />as oidofconstraint I put the OID displayed in pg_admins
propertypain when selecting a constraint. <br /><br />This failed with <br clear="all" /><br />ERROR: could not find
tuplefor constraint 36099<br />SQL state: XX000<br /><br />when I took the OID from UNIQUE and PRIMARY KEY
constraints.<br/><br />Then I moved on and took the OID from FOREIGN KEY constraints, and got results... <br /><br
/><br/>digging in pg_catalog.pg_constraints made me learn that pg_admin shows those OIDs for UNIQUE and PRIMARY key
constraints"off by one", that is:<br /><br />if  I do<br /><br />select pg_get_constraintdef(36100) <br /><br />instead
of<br/><br />select pg_get_constraintdef(36099)<br /><br />I get the needed result....<br /><br />Please find that "-1"
andadd it again :)<br /><br />Best wishes,<br /><br />Harald<br /><br /><br />-- <br />GHUM Harald Massa <br
/>persuadereet programmare<br />Harald Armin Massa<br />Reinsburgstraße 202b<br />70197 Stuttgart<br />0173/9409607<br
/>fx01212-5-13695179 <br />-<br />Python: the only language with more web frameworks than keywords.  

pgadmin-support by date:

Previous
From: Raymond O'Donnell
Date:
Subject: Re: Document for PgAdmin
Next
From: Dave Page
Date:
Subject: Re: Wrong OID for Primary Key and UNIQUE constraints shown in property pane