From: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
---|---|
To: | Harshal Dhumal <harshal(dot)dhumal(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [RM2074][[RM2080]][pgAdmin4] handle large bytea and bytea[] data in datagrid |
Date: | 2017-07-14 13:53:32 |
Message-ID: | CAKKotZTB-iRKSGqi=yhET+APON3sn2=vt+nH=n03-P_vA0JvNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Harshal,
This broke the fetching trigger function parameters logic, take a look at
raise_a_notice() function parameter in screenshot.
In my opinion we just can't just blindly convert everything to place
holder, what if user wants to perform some operation on bytea column like
we are doing in web/pgadmin/browser/server_groups/servers/databases/
schemas/tables/templates/trigger/sql/default/properties.sql to fetch these
arguments?
[image: Inline image 1]
--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Fri, Jul 14, 2017 at 6:43 PM, Harshal Dhumal <
harshal(dot)dhumal(at)enterprisedb(dot)com> wrote:
> Hi,
>
> Please find attached patch to handle bytea and bytea[] data in datagrid.
>
> Now instead of showing actual data we can show placeholders like <binary
> data> and <binary data[]>. Also placeholders will only appear if data
> actually exists otherwise null will be shown.
>
>
> --
> *Harshal Dhumal*
> *Sr. Software Engineer*
>
> EnterpriseDB India: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joao De Almeida Pereira | 2017-07-14 14:24:06 | Re: [pgadmin-hackers][pgaweb][patch] Website patch to add SCSS |
Previous Message | Harshal Dhumal | 2017-07-14 13:13:01 | [RM2074][[RM2080]][pgAdmin4] handle large bytea and bytea[] data in datagrid |