Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bRb3b-0003tC-0n for pgadmin-hackers@arkaria.postgresql.org; Mon, 25 Jul 2016 08:16:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bRb3a-0007Ak-Am for pgadmin-hackers@arkaria.postgresql.org; Mon, 25 Jul 2016 08:16:10 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bRb3Z-0007Ab-OS for pgadmin-hackers@postgresql.org; Mon, 25 Jul 2016 08:16:09 +0000 Received: from mail-io0-x233.google.com ([2607:f8b0:4001:c06::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bRb3W-0008C7-Ri for pgadmin-hackers@postgresql.org; Mon, 25 Jul 2016 08:16:08 +0000 Received: by mail-io0-x233.google.com with SMTP id b62so154997077iod.3 for ; Mon, 25 Jul 2016 01:16:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s2S0Dr1p/lxM3rcsdSm1JGITSwTsPVDmfUS6LqIF7x8=; b=fokqjcCNds+jt/OYjpV0c6kFKtvExPcKJFymHs8iAh2lcImKpyroLfJhx9Vel7At7B eU10kV7PumdlTYtvAuhjWrRvQOigHi0MiFUxTe8/f2HHG8Rkk+6e67f+PZJL3xZrz7xI VJ2Zx+QzGiyK2ZlL9WPkyT6Yocn1NISBy2nPMg3/dJux/zJo1GL0ZK7MnNYvfXljGzkB QblQy9Z1d9JBQxUsmZVhcp1dVs46g0Wjgi2dcKs7hAaUX7r9z/+EotWYzY0m2uDnXwxC piHduBRaJ/J3KXXq1uMYebjI9pNZc7L2vX9+hip+jXIZ7nQnU87/ngTIwdULysOQb2rV cPZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s2S0Dr1p/lxM3rcsdSm1JGITSwTsPVDmfUS6LqIF7x8=; b=AYsVJqmhBcOD/VYjWzV6WAX2sP13pZ/9mqcfqzlZYNUwkldsz+jAGgVhO76GXMOhtY uBxjtimqcD9aOQ6KDsFjTIydcM1rs4PwRJIk/qHvVdlQ+HYWo70W8NiREPlMJMcU02XF 2PoCaXCi58bFwVoSZJP9LI6waG9zuNHS9OBKG8BN10tGACdgXCjDbYtKYM0dgNl5admV fUGcu7t8w9aJGgmT8inxqebOVjxfX6pBYfckJ4hK4mWHEyFbqqjoDFpB+m3FR7oXOiqi NCuGRW9y7dk2uA7IlkmFksf/G4moXLzYga1TgyadgLtyrDMOIo4PHYZss2ebYtAvlqmA Bo5g== X-Gm-Message-State: AEkoousyV4Kf5QMZH8Tej6l26QoRUv6GgTNA3V5ikIR71hzCL3P4GRgx9P+xuIz4Uxg0zGeeCKNEzW5SGji2fA== X-Received: by 10.107.160.204 with SMTP id j195mr19267275ioe.70.1469434565798; Mon, 25 Jul 2016 01:16:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.208.97 with HTTP; Mon, 25 Jul 2016 01:16:04 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Mon, 25 Jul 2016 09:16:04 +0100 Message-ID: Subject: Re: [pgAdmin 4 UI bug] unable to add foreign keys through the UI To: Michael Meerschaert Cc: pgadmin-hackers Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org Hi Thanks - please log this here: https://redmine.postgresql.org/projects/pgadmin4/issues/new (if you do it rather than me, you'll get emailed when there are updates). Cheers, Dave. On Sat, Jul 23, 2016 at 7:04 PM, Michael Meerschaert wrote: > Hi, > > I'm sorry if there is an official bugzilla or something for reporting bugs, > but from the comments here it seems like this is the preferred way to report > issues. > > From the Create - Table dialog, I am unable to add foreign keys. Here's step > by step what i'm trying to do: > > Click Constraints > Foreign Key and click Add > A row appears where i can click edit, trash or enter a name, I also see a > red banner at the bottom saying "Please Specify Columns for foreign key > The columns field is greyed out, so I click the edit icon (If i enter a > name, it populates to the name field under general) > Click Columns > Select the local column > select the references table > > As a side note, if there is only 1 other table in the schema, the > "references" drop down will default to it, but you cannot select a column > from "referencing" from the default dropdown option. You must first change > the "references" option, which is impossible if there is only 1 table. Also, > even if there are multiple tables, and the references table is correct, you > still have to change it to another option then change it back to get the > columns in the "referencing" dropdown to show up. This bug has a workaround, > but still feels like a bug. > > select the column for "Referencing" > click add > nothing happens, the red banner that says please specify columns for foreign > key is still there. > > I can just execute raw SQL to add the constraints, and the UI picks up on > the fact that the constraints are there, but I'm still unable to add new FKs > through the UI. Also, when I click edit on an existing FK, all the options > on the columns and Action tabs are greyed out. > > I'm running windows 10 64-bit. > > > -- > -Mike -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers