Re: PATCH: Fix the issue for saving query output as CSV - Mailing list pgadmin-hackers

From Dave Page
Subject Re: PATCH: Fix the issue for saving query output as CSV
Date
Msg-id CA+OCxozJ3eejW+LN7KN5VzxzBNGGpwoO=qZ9VMFi_DTpF82crg@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: Fix the issue for saving query output as CSV  (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>)
Responses Re: PATCH: Fix the issue for saving query output as CSV
List pgadmin-hackers
On Tue, Jun 28, 2016 at 10:33 AM, Murtuza Zabuawala
<murtuza.zabuawala@enterprisedb.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
Backbonemodels & 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


pgadmin-hackers by date:

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