> From: sqlite-users > [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On > Behalf Of Olivier Mascia > > Considering: > > CREATE VIRTUAL TABLE temp.t1 USING csv(filename='thefile.csv'); > > Is there any way to teach the csv extension to use ';' > instead of ',' as the column delimiter, getting away from the > strict RFC4180 definition? While on the topic of Excel generated CSV, I had occaision to do this a year-and-a-half ago, so let me forewarn you of a couple other things: * quoting; excel will sometimes enclose a field in quotes, and sometimes not, depending on the content therein * quoting; excel uses 'double quoting' for 'escaping'; i.e. two quotation marks in a row are interpreted as a quote char, rather than the arguably more common backslash style escaping * multi-line fields; your excel document can have cells which contain multiple lines (i.e. embedded carriage returns)
Anyway, all this led me in my case to write a state machine to read in a logical 'line' of text, and crack it into fields. That being said, just now taking a peek at the current implementaion in the sqlite codebase: ext\misc\csv.c:197 Is a commment /* Read a single field of CSV text. Compatible with rfc4180 and extended ** with the option of having a separator other than ",". So maybe that implementation is already enhanced to accommodate those cases, but the capability is simply not exposed through parameters to the CREATE VIRTUAL TABLE CSV (...) So maybe one would just need to modify the csvtabCreate to process some additional parameters and propagate those settings to the implementation. -dave _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
