Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1axuel-00033k-QJ for pgadmin-hackers@arkaria.postgresql.org; Wed, 04 May 2016 11:07:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1axuek-0007hw-Nr for pgadmin-hackers@arkaria.postgresql.org; Wed, 04 May 2016 11:07:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1axuek-0007hn-8X for pgadmin-hackers@postgresql.org; Wed, 04 May 2016 11:07:50 +0000 Received: from mail-ig0-x236.google.com ([2607:f8b0:4001:c05::236]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1axueb-0000rv-Oo for pgadmin-hackers@postgresql.org; Wed, 04 May 2016 11:07:48 +0000 Received: by mail-ig0-x236.google.com with SMTP id bi2so143707783igb.0 for ; Wed, 04 May 2016 04:07:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=fJbF+r5gABx6IoePihGl/QxHx7/kO33skYeTk63Lv4Q=; b=FU9cViFsVSOxobj6YUf6ZEpUl6FQOoCC4sw8025haLfElCDIBwopJIyO55pEY95ZB+ lHW7XL7Y9I8mGcnxwWOtMS1SOoseFoRgv0yvTz0jA7vfXm0IPO/bepGKbmxMa317+poq qeKcAZLKvIeWNxlO6ya+w0Qk4TskabhSH2v/3WQcNulNVvwWoAxCfDcsewRCtHrnU7GC g+j4VmtU4ggQyyKNpp3IVykBJOJy3OBnF5dyzLBH6tVQGGfjH7zfP5kPTjW/Cnm5GWnN nwsMhz5d0yH2h8USMvWmicetMeoZATR83dqz4BWOz3Kfv72khlTi84l0sO7z7om4K6kO PPBQ== 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:date :message-id:subject:from:to:cc; bh=fJbF+r5gABx6IoePihGl/QxHx7/kO33skYeTk63Lv4Q=; b=SUe7YZbnlT3bC7hH8qlKYe2PXwMBSWU55AoPMvboDIh2MmxF5pKX7/PgVOc3V30rZA 0+PMBtB5brsBlCEWF8om8KIzjze11savmFpaspuvvHJjF1HHQeG8cXkpyTmrdXAYokXn gZVfEFh9VCmFTRqZ7+fKMDvCYh+tlXgmru2UHcSvkSwMKf5Tzn9JwkBFwVIjvXKkI+vQ NAAW2dKvCjKrQ/dZt46FxvhSt2s4yD0BFr7HGDcsAsQTYmneeNnjy5Ip1GkXsIB941Ew kzn4hCcR+sFPcoRkXRWmh7DZrC25l9/Crl8v88tDuoTU8rOFKGKsQ3bC/n1ax+Kh1pzO iIGA== X-Gm-Message-State: AOPr4FXtJjuxuyDHHKpLGJJz0aG4sTst4e7o1A/Dfra7W4RdvowmqXfxW51ctZ2NhC3PRGK6IU6BIq+IqOcoO6tIiQM33pEdv+KeqvGz/vOiw9CV2EczabYvJFI9CoM6xjJZriqW35k8B1VnkTKE0AfNG0Dy9dAfxnnb7HHznE527WEZaJEDGIVAsVh3at0e8J2wCj4nLg== X-Received: by 10.50.34.130 with SMTP id z2mr32276735igi.82.1462360059887; Wed, 04 May 2016 04:07:39 -0700 (PDT) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com. [209.85.223.182]) by smtp.gmail.com with ESMTPSA id vh5sm1116613igb.21.2016.05.04.04.07.38 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 May 2016 04:07:38 -0700 (PDT) Received: by mail-io0-f182.google.com with SMTP id f89so50101477ioi.0 for ; Wed, 04 May 2016 04:07:38 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.148.210 with SMTP id w201mr9973369iod.63.1462360057741; Wed, 04 May 2016 04:07:37 -0700 (PDT) Received: by 10.64.105.131 with HTTP; Wed, 4 May 2016 04:07:37 -0700 (PDT) In-Reply-To: References: Date: Wed, 4 May 2016 12:07:37 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [pgAdmin4] [Patch]: Foreign Table Module From: Dave Page To: Khushboo Vashi 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 On Wed, May 4, 2016 at 7:51 AM, Khushboo Vashi wrote: > Hi Dave, > > In PG 9.5, for Foreign Table Editing, below new functionalities are added: > > ALTER [ COLUMN ] column_name SET STORAGE { PLAIN | EXTERNAL | EXTENDED | > MAIN } > DISABLE TRIGGER [ trigger_name | ALL | USER ] > ENABLE TRIGGER [ trigger_name | ALL | USER ] > ENABLE REPLICA TRIGGER trigger_name > ENABLE ALWAYS TRIGGER trigger_name > SET WITH OIDS > SET WITHOUT OIDS > > As per our conversation yesterday, we need to incorporate these > functionalities into pgAdmin4. Here I have some queries regarding the > implementation. Under the Foreign Table Node, we don't have separate nodes > for columns, triggers and constraints as table. So in order to add above > Trigger related functionalities, we will have to add Trigger Node under the > Foreign Table. And If we add Triggers, then Do we need to add Columns and > Constraints as separate nodes under the Foreign Table? Following discussion with Ashesh and some further thought, please put these enhancements on hold. We'll add them in a future release, as it's just too much work to do right now. Please add a TODO file to the root directory of pgAdmin 4, and add these as items for later completion. Thanks. -- Dave Page VP, Chief Architect, Tools & Installers EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company Blog: http://pgsnake.blogspot.com Twitter: @pgsnake -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers