public inbox for [email protected]help / color / mirror / Atom feed
Require suggestions on feature 4011 3+ messages / 2 participants [nested] [flat]
* Require suggestions on feature 4011 @ 2025-08-08 10:11 Pravesh Sharma <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Pravesh Sharma @ 2025-08-08 10:11 UTC (permalink / raw) To: pgadmin-hackers 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Require suggestions on feature 4011 @ 2025-08-14 09:05 Pravesh Sharma <[email protected]> parent: Pravesh Sharma <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Pravesh Sharma @ 2025-08-14 09:05 UTC (permalink / raw) To: pgadmin-hackers Hi Hackers, Any suggestions on the above issue. Thanks, Pravesh On Fri, Aug 8, 2025 at 3:41 PM Pravesh Sharma < [email protected]> 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 > ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Require suggestions on feature 4011 @ 2025-08-14 09:36 Aditya Toshniwal <[email protected]> parent: Pravesh Sharma <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Aditya Toshniwal @ 2025-08-14 09:36 UTC (permalink / raw) To: Pravesh Sharma <[email protected]>; +Cc: pgadmin-hackers Hi Pravesh, I think we'll have to load the binary data in the backend at least like you mentioned. It will increase memory consumption, so we'll have to make this feature preference based with clear mention of the memory requirements in the help string and by default disabled. On Thu, Aug 14, 2025 at 2:35 PM Pravesh Sharma < [email protected]> wrote: > Hi Hackers, > > Any suggestions on the above issue. > > Thanks, > Pravesh > > On Fri, Aug 8, 2025 at 3:41 PM Pravesh Sharma < > [email protected]> 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 >> > -- Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Staff SDE II | *enterprisedb.com* <https://www.enterprisedb.com/; "Don't Complain about Heat, Plant a TREE" ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-08-14 09:36 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-08-08 10:11 Require suggestions on feature 4011 Pravesh Sharma <[email protected]> 2025-08-14 09:05 ` Pravesh Sharma <[email protected]> 2025-08-14 09:36 ` Aditya Toshniwal <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox