Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDQcE-0005CK-JS for pgadmin-hackers@arkaria.postgresql.org; Wed, 24 May 2017 07:21:54 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dDQcE-0008QQ-49 for pgadmin-hackers@arkaria.postgresql.org; Wed, 24 May 2017 07:21:54 +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 1dDQcD-0008QH-KT for pgadmin-hackers@postgresql.org; Wed, 24 May 2017 07:21:53 +0000 Received: from mail-pf0-x22a.google.com ([2607:f8b0:400e:c00::22a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dDQcA-0008Bi-3q for pgadmin-hackers@postgresql.org; Wed, 24 May 2017 07:21:52 +0000 Received: by mail-pf0-x22a.google.com with SMTP id n23so134941003pfb.2 for ; Wed, 24 May 2017 00:21:49 -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:from:date:message-id:subject:to :cc; bh=ZbNfnN7bLjoEiaGep1l9OUv4Vze6YLWEAqK4FtFJAtU=; b=w53MAt2Owf+Z3hsw7b1qvA4N9Zbl13QsausSvhTH7leU16qLphZHdak2+wRrsX5CFd JMaexgxJxHzq4PvPiRPHLM45KckUknx8/1IGslto+tGtTOgybswChdvx9sjYMI3J49YQ C4ftdu9RBd4EL3ezPznCZiTpRuTo62UV7JzeZEQLEgqRl5b0lud7ueiHF1atN1+oXOUf lvSif8LCAddvYLE3IF42TuvitkQPBJke4dhcOD7/7kuDAF1MOS6MTLPL+/pe9fXGBlvu KAiYE1mvAnJgNnG6PF7PiPgE2en+9YL8i1Tf4tAmtzOf97PCI8geZxk9gJ0jt6EzsRhg WJXg== 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=ZbNfnN7bLjoEiaGep1l9OUv4Vze6YLWEAqK4FtFJAtU=; b=mIUYHh+Sd1BPdSCEutXPs9C8C/PS9h4XNDqXtFp0oCunNi7RK1nq/ENYFKxDQf9gyK ZhHuP2AKUBxVrQkbVxuDNPn9BKX2a6/mShJCIoMW1IRwa7z8mAmwCmWQvLp/X2Tk7I8V IvYg6FKvsXNtC3b3ALZLyjkzT1WQ3wbObPZPYe8l3ad3mf8sAE285k28pWWbq8qY+hir ZVfnfDvLvxfh9+kWF94vRje5evVptMERRlEmpd63HP+44eg7vDzC2Nh6BUAaRg/s3l9V LNOC8g6l/O72bkRTrRkz5h8TYzksWk/rb0a50pDzeOjJL7TrNFUTyUzGJ/jK8IruNpWx Ma1w== X-Gm-Message-State: AODbwcDeiD0pEAS5UuGeTNRXEWOzo3W6iTuTfYpydT04DogGv1PDv9+l gv7GnLw+DDlM4K6I5sZlI0TeQcU8aeaK X-Received: by 10.98.70.17 with SMTP id t17mr37076894pfa.229.1495610508788; Wed, 24 May 2017 00:21:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.170.75 with HTTP; Wed, 24 May 2017 00:21:48 -0700 (PDT) In-Reply-To: References: From: Akshay Joshi Date: Wed, 24 May 2017 12:51:48 +0530 Message-ID: Subject: Re: Declarative partitioning in pgAdmin4 To: Shirley Wang Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="94eb2c0b79d6195d7a05503ff581" X-Pg-Spam-Score: -1.9 (-) 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 --94eb2c0b79d6195d7a05503ff581 Content-Type: text/plain; charset="UTF-8" Hi Shirley On Tue, May 23, 2017 at 7:39 PM, Shirley Wang wrote: > It's less about implementing what's easy, and more about implementing what > we know for sure will provide user value. > Agreed, but if that feature(expression) is available in postgresql then users/QA will ask why that is not present in pgAdmin4. If implementation is complex then we could think to include it or not, if we will provide that its upto the user they want to use it or not. > > Given that in the expression you used, the variables 'a' and 'b' have > undefined values, there's still a chance that we're missing a large chunk > of context for successful implementation. > > Could you explain what 'a' and 'b' represent? > Where would users find values for 'a' and 'b'? (are they columns?) > a and b are columns. > What is the use case for partitioning by (a+b)/2? > How frequently will people partition this way? > That is just an example of expression, there is no use case for above example. > > It's possible to design for the range and list partitions and know we can > achieve success because we understand how users would go through this > workflow. Not sure about expressions. > > > > -- *Akshay Joshi* *Principal Software Engineer * *Phone: +91 20-3058-9517Mobile: +91 976-788-8246* --94eb2c0b79d6195d7a05503ff581 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Shirley

On Tue, May 23, 2017 at 7:39 PM, Shirley Wang &= lt;swang@pivotal.io> wrote:
It&= #39;s less about implementing what's easy, and more about implementing = what we know for sure will provide user value.=C2=A0





--
Akshay Joshi


<= b>Phone: +91 20-3058-9517
Mobile: +91 976-788= -8246
--94eb2c0b79d6195d7a05503ff581--