| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Matthew Kleiman <mkleiman(at)pivotal(dot)io> |
| Cc: | Surinder Kumar <surinder(dot)kumar(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, George Gelashvili <ggelashvili(at)pivotal(dot)io> |
| Subject: | Re: [pgAdmin4][Patch][RM2257]: Query tool - Insert row doesn't use default values |
| Date: | 2017-04-07 08:53:39 |
| Message-ID: | CA+OCxow5Dd4dkdbWJ6vA8+=eTdmHZU5sT757Pmee4+mD-y3pPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Tue, Apr 4, 2017 at 5:37 PM, Matthew Kleiman <mkleiman(at)pivotal(dot)io> wrote:
> Hi Surinder,
>
> We looked at your fix for default values in the query tool editor.
>
> We think the user experience could be further improved by seeing the actual
> default value instead of the empty cell.
Agreed.
> As an intermediate step, there would be user value in seeing "[default]"
> instead of the blank cell (or what used to be "[null]").
Also agreed. Surinder, please add the [default] label in your next
update. We'll look at immediately returning values in the future,
though that may not actually be possible without saving the row
(defaults may not be constant, they could be expressions).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murtuza Zabuawala | 2017-04-07 08:55:42 | Re: [pgAdmin4][PATCH] Fix the issue in browser tree |
| Previous Message | Dave Page | 2017-04-07 08:51:49 | Re: [pgAdmin4][Patch][RM2257]: Query tool - Insert row doesn't use default values |