Instead of trying to conform to MS-Excel's csv format, wouldn't it be better to write an import from .xls (or .ods if that is an open standard) directly?
That way each cell's value can be bound to a position holder in a query. No more fussing with "In this country we use this symbol to denote decimals", "my data has special characters or line feeds inside a cell" etc. regards, Adam On Thu, Jul 30, 2015 at 2:32 PM, Bernardo Sulzbach <mafagafogigante at gmail.com> wrote: >> My point is that I have seen so many emails regarding this incorrect csv >> import, that it would be so easy for us if it just simply works in the CLI >> and delivered in standard in the sqlite3 executable. > > I don't think I understand what you mean by this. Also, most of the > problems seems to arise from the fact that CSV is just too weakly > specified. See how better defined JSON is and how it solves a lot of > problems (not suggesting JSON here). > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users -- -------------- VerifEye Technologies Inc. 151 Whitehall Dr. Unit 2 Markham, ON L3R 9T1
