| From: | Pravesh Sharma <pravesh(dot)sharma(at)enterprisedb(dot)com> |
|---|---|
| To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Require suggestions on feature 4011 |
| Date: | 2025-08-14 09:05:10 |
| Message-ID: | CA+36bxE5YHZgyb5Ps0AzFsDR4GAPV_z3SQuAk_DBEc6N=X4Z3w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Hackers,
Any suggestions on the above issue.
Thanks,
Pravesh
On Fri, Aug 8, 2025 at 3:41 PM Pravesh Sharma <
pravesh(dot)sharma(at)enterprisedb(dot)com> wrote:
> Hi Hackers,
>
> I'm working on feature #4011
> <https://github.com/pgadmin-org/pgadmin4/issues/4011>, which involves
> exporting and importing BLOB (bytea) data. I've checked its feasibility and
> these are the challenges I'm facing:
>
> Currently, we simply return the string "binary data" for bytea columns,
> and we don't load the actual binary data at all. If we want to download
> this data, we can bring it to the cursor, but when returning it to the
> front end, we'll still send the string "binary data" Upon a user's
> request to download, we'll fetch it from the cursor and return it.
>
> The main challenge I'm facing is how we'll identify the row from which the
> download needs to happen if there's no primary key in the table.
> Additionally, keeping binary data in memory could cause performance issues.
> For this reason, we can make it a preference-based option.
>
>
> Please let me know your thoughts/suggestions.
>
>
> Thanks,
>
> Pravesh
>
> --
>
>
> Pravesh Sharma
>
> Senior SDE
>
> +91 9406461406
>
>
> enterprisedb.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aditya Toshniwal | 2025-08-14 09:36:20 | Re: Require suggestions on feature 4011 |
| Previous Message | Pravesh Sharma | 2025-08-08 10:11:39 | Require suggestions on feature 4011 |