Re: SQL output to csv -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: SQL output to csv
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Wed, 4 Dec 2013 17:11:43 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, Dec 4, 2013 at 4:30 PM, Narayanan Pillai <strqst400@xxxxxxxxx> wrote:

I know this is not the right forum to discuss RFCs, but I interpreted
that comment to mean - don't expect excel produced CSVs to look
like this spec. From experience, excel does not produce CSVs with
double quoted fields

The RFC states that "some programs, such as Microsoft Excel, do not
use double quotes at all". But Excel DOES use double quotes whenever
the data contains commas, double-quotes, or newlines.

John

Follow-Ups:

Re: SQL output to csv , Narayanan R Pillai

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.