| From: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgAdmin4][PATCH] To fix the issue with displaying bigint[] values in query tool |
| Date: | 2017-04-20 13:48:05 |
| Message-ID: | CAKKotZQRKmFZurFc8X_3sebqP87-a3ChSZJj6fOBr4kkUNevvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
That is strange.
I tested on PG9.6 and it was working properly, What is the your PG version?
--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Thu, Apr 20, 2017 at 7:06 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>
> On Fri, Apr 14, 2017 at 2:28 PM, Murtuza Zabuawala <murtuza.zabuawala@
> enterprisedb.com> wrote:
>
>> Hi,
>>>
>>> PFA minor patch to fix the the issue with bigint[] array values as JS
>>> truncates long numbers from array object.
>>> RM#2272
>>>
>>
> Hi
>
> As far as I can see, this doesn't work as expected. The "bad" column is
> interpreted as numeric[] on my machine, which I assume needs to be added to
> the list as well?
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joao Pedro De Almeida Pereira | 2017-04-20 14:45:37 | Re: [patch] Move to Alembic migration system |
| Previous Message | Dave Page | 2017-04-20 13:36:09 | Re: [pgAdmin4][PATCH] To fix the issue with displaying bigint[] values in query tool |