2014-03-11
| ||
13:17 | • Fixed ticket [c25aab7e7e]: The ".import" command does not parse CSV correctly. plus 3 other changes (artifact: 5733c490a9 user: drh) | |
2011-10-13
| ||
13:20 | • Ticket [c25aab7e7e]: 2 changes (artifact: 8a44239e2e user: drh) | |
2010-05-12
| ||
17:53 | • Ticket [c25aab7e7e]: 2 changes (artifact: 3d07a0d47a user: anonymous) | |
2010-01-06
| ||
15:37 | • Ticket [c25aab7e7e]: 1 change (artifact: 8fce5cd8f8 user: anonymous) | |
2009-11-04
| ||
23:53 | • Ticket [c25aab7e7e]: 1 change (artifact: d6615d6c42 user: shane) | |
2009-10-27
| ||
21:17 | • Ticket [c25aab7e7e]: 1 change (artifact: 6df67dd647 user: rogerb) | |
20:00 | • Ticket [c25aab7e7e]: 1 change (artifact: bb94d6842d user: rogerb) | |
2009-10-14
| ||
11:15 | • Ticket [c25aab7e7e]: 1 change (artifact: 7466c10062 user: anonymous) | |
2009-10-06
| ||
18:10 | • Ticket [c25aab7e7e]: 2 changes (artifact: 1a724b756f user: rogerb) | |
2009-08-13
| ||
15:19 | • Ticket [c25aab7e7e]: 5 changes (artifact: 1dae0db427 user: drh) | |
14:01 | • New ticket [c25aab7e7e]. (artifact: 00da186adb user: anonymous) | |
Ticket Hash: | c25aab7e7ea55c861313076cae9257fc8f3fbdc0 | ||
Title: | The ".import" command does not parse CSV correctly. | ||
Status: | Fixed | Type: | Feature_Request |
Severity: | Important | Priority: | Low |
Subsystem: | Shell | Resolution: | Fixed |
Last Modified: |
2014-03-11 13:17:03 11.11 years |
Created: |
2009-08-13 14:01:42 15.68 years |
Version Found In: | 3.6.23.1 |
Description: | ||||
when importing CSV data, in text fields separated by double quotes, commas are treated as field separator.
live example: 770,"011",2002,2001247,3,4,"6/SOCJ,",1,0,20020131,122602,20020131,1,"FBLI" in 7th field, which is "6/SOCJ," the comma inside the quotes is mis-interpreted as field separator, and application submits error: FGLEDX line 136090: expected 14 columns of data but found 15 In case you need more information, please contact me at rafal@pies.pl. Best regards, Rafal Stanilewicz drh added on 2009-08-13 15:19:32: There is no such thing as a "CSV" standard. Different programs do different things. There might be users that depend on the current behavior. If we fix this for the OP, it could cause problems for others. So it is unclear whether or not we should do anything for this. We will simply leave the ticket open for the time being. rogerb added on 2009-10-06 18:10:35: It would be reasonable to expect that whatever SQLite exports would import as exactly the same data. anonymous claiming to be PM added on 2009-10-14 11:15:47: rogerb added on 2009-10-27 20:00:06: http://www.sqlite.org/cvstrac/tktview?tn=1506 rogerb added on 2009-10-27 21:17:53: anonymous added on 2010-01-06 15:37:44: http://tools.ietf.org/html/rfc4180 anonymous added on 2010-05-12 17:53:05: I propose these modifications to make sqlite3 more easy to use (export/import with ".mode csv"). In "src/shell.c" Version 3.6.23.1 :
|