Skip site navigation (1) Skip section navigation (2)

[pgAdmin III] #289: Foreign key UI bug

From: "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: [pgAdmin III] #289: Foreign key UI bug
Date: 2010-11-20 11:25:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
#289: Foreign key UI bug
 Reporter:  Aren Cambre  |       Owner:  gleu
     Type:  bug          |      Status:  new 
 Priority:  minor        |   Milestone:      
Component:  pgadmin      |     Version:  1.12
 Keywords:  foreignkey   |    Platform:  all 
 I found a UI bug when creating a foreign key.

 When creating a primary key, all you have to do is select the column in
 the *Columns* tab of the dialog. You don't have to fill out any other
 fields; pgadmin appears to take care of this for you.

 It seems then that with a foreign key, all you should have to fill out is
 fill out the *References* field in the *Properties *tab, then in the
 *Columns* tab just select the relevant columns. If I do this and press OK,
 I get this error:

 *An error has occurred:*
 *ERROR: relation "fki_" already exists.*

 If I go back to the *Properties* tab and enter something into the *Name*
 field, then press *OK*, it works.

 The problem: I don't need to enter anything in the *Name* field of primary
 key dialogs, but I do with foreign key dialogs. Can it be consistent where
 I don't need to enter a *Name* field of the foreign key, either.

Ticket URL: <>
pgAdmin III <>
pgAdmin III


pgadmin-hackers by date

Next:From: pgAdmin TracDate: 2010-11-20 17:49:38
Subject: Re: [pgAdmin III] #289: Foreign key UI bug
Previous:From: Guillaume LelargeDate: 2010-11-20 11:13:10
Subject: Re: Ticket 266: Unable to backup table when quotation marks used in the name

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group