Commas in data cause problems when exporting as CSV

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Upload or create a database where one or more fields contains text including 
a comma.
2. Export a copy of the database as a CSV file.
3. Open the resulting file.

What is the expected output? What do you see instead?
The default expectation is that one field in the ORDS database will translate 
into one field/column/Excel cell in the exported version. However, if a field 
contains a comma, this will be treated as a delimiter during the export 
process, and (if viewed using Excel) everything after the comma will appear in 
the next column along. This looks as though it has the power to cause 
significant problems - e.g. subsequent fields being misaligned, etc.

(Not sure who's the appropriate person to deal with this - please feel free to 
reassign it.)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by meriel.p...@gmail.com on 8 Dec 2014 at 3:10

[GoogleCodeExporter]

This is being reported by real users. Is there any way to 'escape' comma 
characters within fields when exporting?

Original comment by jajwil...@gmail.com on 2 Mar 2015 at 4:26

• Changed state: New
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I've just noticed that when saving as standard .csv from Excel, Excel puts 
double quotes "" around any fields that contain commas. ORDS doesn't do this. 
It probably should.

Original comment by jajwil...@gmail.com on 2 Mar 2015 at 4:46