Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cRujY-00056k-8F for pgadmin-hackers@arkaria.postgresql.org; Fri, 13 Jan 2017 05:49:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cRujX-0006Ch-4R for pgadmin-hackers@arkaria.postgresql.org; Fri, 13 Jan 2017 05:49:03 +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 1cRujJ-0005iD-75 for pgadmin-hackers@postgresql.org; Fri, 13 Jan 2017 05:48:49 +0000 Received: from mail-io0-x231.google.com ([2607:f8b0:4001:c06::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cRujF-0005Cc-71 for pgadmin-hackers@postgresql.org; Fri, 13 Jan 2017 05:48:48 +0000 Received: by mail-io0-x231.google.com with SMTP id j13so36205744iod.3 for ; Thu, 12 Jan 2017 21:48:44 -0800 (PST) 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=+3ox2Ccj8fTTUwv1BvOjmTF2unmCaQZ3YDPnnt8cfss=; b=Gqf884SgVz79PAegJjlPFyCGht6Hqe4K2nhx/yewCgP83ViDvqfsKX2qHhq56hdscJ No1wt2jZJ8dz7S85hVmJjFR0ybW1ydmC1XcJokyEgB4DjcNDo9qOabSc6ehalGfS7S6y wF1FDlU+H5DUN/POSnqrvI8u6KFSk0GKlbmIPtpDkJG6Pqg2T6haUR9x65QZOCwvvJfL t8kShDMSrYsouRjeaSbGPMkEcPM0J8glBlJsEDchqckvc6KgVooGWWDxIqzSN1YIccCf W/8ppn3I6oL9a44GgGO3FrwW9gglpgV8HvLZydhfH4gH2yVVnrutBPvXwqSO8/3ezBQG oPfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+3ox2Ccj8fTTUwv1BvOjmTF2unmCaQZ3YDPnnt8cfss=; b=UeCeVwYYIeYgfzrrV9XKTxh6s2xORJGkfSckt+jz/vbyPkDOv4Pse4W8e5IewkgyGx xS8nRxwF3yQ7PS9skxxKWyT/1bl9Z3C4kSLawMYNNjWf+yvkevzlyiuoAszNOM4ekrTe D8qC84YI4YHYegakzED0T6IYFDKQ/maHS/iZLqDVfESHmjTr529XR0jvJxr1A2YONvNf VROYDzebFockwBZ6IwKOo8NJlnXl0WNVBI7/VV6EkCihvu77liHPUVGchhubeAAZKrpl MRF8sQzZ6JEMgb9yWOQszwh8PpTb1d/vNKSDnkD6bCPAPob2xh/DlJjTRnjsdFtGVCEw HBsw== X-Gm-Message-State: AIkVDXL7lr77XfQA13myHQGE3RlJMGmoUUeILsFPaYGAUGvDsFckFwI5SxR319bRsMNjvoJfvhwH+FlzkUALAA== X-Received: by 10.107.18.230 with SMTP id 99mr15706162ios.45.1484286522717; Thu, 12 Jan 2017 21:48:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.224.198 with HTTP; Thu, 12 Jan 2017 21:48:42 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Fri, 13 Jan 2017 11:18:42 +0530 Message-ID: Subject: Re: Driver Module To: George Gelashvili Cc: Robert Eckhardt , "pgadmin-hackers@postgresql.org" , "plumadmin@pivotal.io" , Ashesh Vashi 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 Thu, Jan 12, 2017 at 8:18 PM, George Gelashvili wrote: > Hi Dave, > > We looked through the places where there is existing version checking and > there isn't a ton of it. That's because we went to great lengths to minimise it in pgAdmin 4. It's mostly confined to template selection for SQL now. > Our current plan for supporting Greenplum in > pgAdmin4 was not necessarily to support all the features of pgAdmin4, but to > at least get the core functionality working. > I'm not too concerned about there being a ton of switches, because I don't > think most features will need to be disabled. We will also likely make > changes to Greenplum to support certain features like query plans rather > than doing all the changes on the pgAdmin4 side. OK. From my perspective though, I have to ensure that what we offer in the community is a good experience. If it's not appropriate or necessary to support a feature in GP, that's fine - but it needs to be disabled to prevent users reporting bugs to us > What I would like to see though is version checking that happens in one > place and is not tied exclusively to either flavor or version, but to a > combination of the two. E.g. Greenplum 5.0 might support a feature that is > not supported in 8.3 postgres. Can you do a rough assessment of how many 'features' we'd be likely to need to have the PG driver advertise? That would give a better idea of the extent of the work involved. In principal I'm not against the idea of having a function in each driver that allows us to check for the presence of a given feature, including by-version as required. What I'm against is that becoming a mess of spaghetti... -- 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