Re: PATCH: Fix the issue for saving query output as CSV
От | Dave Page |
---|---|
Тема | Re: PATCH: Fix the issue for saving query output as CSV |
Дата | |
Msg-id | CA+OCxozJ3eejW+LN7KN5VzxzBNGGpwoO=qZ9VMFi_DTpF82crg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PATCH: Fix the issue for saving query output as CSV (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>) |
Ответы |
Re: PATCH: Fix the issue for saving query output as CSV
|
Список | 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 по дате отправления: