Re: PATCH: Fix the issue for saving query output as CSV

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: Fix the issue for saving query output as CSV
Date: 2016-06-29 10:10:33
Message-ID: CA+OCxozJ3eejW+LN7KN5VzxzBNGGpwoO=qZ9VMFi_DTpF82crg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Tue, Jun 28, 2016 at 10:33 AM, Murtuza Zabuawala
<murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:
> Yes Dave, I agree that downloading files has been supported in browsers since long .
>
> But in general we send request & then receives files from web server but in our case we are fetching our data from Backbone models & then converting it to CSV format for downloading as a file at client side in browser itself.

If Safari doesn't support client-side saving of files, then I have to
wonder if our runtime will either - both are webkit based.

So I guess the next question to ask is; why don't we just generate the
CSV on the server side?

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2016-06-29 10:19:08 pgAdmin 4 commit: Fix intermittent CodeMirror rendering issue. Fixes #1
Previous Message Dave Page 2016-06-29 10:07:19 Re: PATCH: 'serial' like types were missing while creating table/column (pgAdmin4)