Re: Declarative partitioning in pgAdmin4

Hi Shirley

On Tue, May 23, 2017 at 7:39 PM, Shirley Wang <swang(at)pivotal(dot)io> 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*