From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgAdmin4][Patch]: Feature test for PG Data-types in Query Tool |
Date: | 2017-05-11 09:11:11 |
Message-ID: | CA+OCxowuS9S95KNFd0=H6Bmec7ZNx70QQpE7n_N7VODEHfuY2w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Thu, May 11, 2017 at 6:38 AM, Khushboo Vashi <
khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:
> Hi,
>
> As we have been facing many issues with different data-type display in
> Query Tool output, Dave suggested to write the feature test for the same.
>
> I have started with some basic set of data-type values and will add more.
> Please find the attached initial patch for the same.
>
Some thoughts:
- Instead of sleeping, which is almost always a bad design, can we wait for
objects to appear?
- Currently you're testing each datatype with an individual query, e.g.
SELECT 32768;
I would suggest we test all datatypes at once, e.g.
SELECT 32768, 43723489023489, '2017-09-12 15:34:11', 12345.56;
etc. That will massively reduce the time taken to execute the tests (which
is a big concern).
- Shouldn't we be casting the values in the SELECT, so we (and the
database) know exactly what we're expecting? e.g.
SELECT 32768::int, 43723489023489::bigint, '2017-09-12 15:34:11':timestamp,
12345.56::numeric(8,4);
That would also allow us to verify the type name displayed in the column
headers.
Thanks!
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2017-05-11 09:15:31 | Re: [pgAdmin4][Patch]: Feature test for PG Data-types in Query Tool |
Previous Message | Dave Page | 2017-05-11 08:59:30 | Re: [pgAdmin4][Patch][RM2257]: Query tool - Insert row doesn't use default values |