Re:

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Cristinel Angheluta" <acristi(at)mymail(dot)ro>
Cc: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re:
Date: 2005-11-04 11:13:17
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC391E@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Cristinel Angheluta [mailto:acristi(at)mymail(dot)ro]
> Sent: 04 November 2005 10:30
> To: Dave Page
> Subject: Re: [pgadmin-support]
>
>
> No I didn't get an error message.
> On "New Foreign key" dialog I'm not able to see any of the
> referencing
> table's fields( bottom most combobox on "Colums" tab). That's
> why I told
> you I'unable to create foreign keys.
> On "Properties" tab -> "References" combobox, all tables
> (except publics'
> ones) don't have as prefix the schema name (ex. schema2.table2).

Hmm, sorry - I still can't reproduce this or any other problems when
creating fkeys from either the table dialogue or when directly using the
foreign key dialogue.

Andreas (or anyone else) can you reproduce this, or think of any
cisrcumstances in which it might happen?

> One more thing that I discovered in 1.4.0 RC1 is that
> creation of a third
> schema helped me to solve this issue. Even if you delete/drop
> the third
> schema "New Foreign key" dialog works properly after that.

Hmm, I wonder if this is a refresh thing - you didn't create the
referenced table through the SQL dialogue, so it's not actually found
until the tree is refreshed perhaps?

Regards, Dave.

Responses

  • Re: at 2005-11-04 13:38:33 from Andreas Pflug

Browse pgadmin-support by date

  From Date Subject
Next Message Joost Kraaijeveld 2005-11-04 11:24:30 Debian AMD64 compile problem
Previous Message Dave Page 2005-11-04 09:05:08 Re: