Le jeudi 30 juillet 2015, Scott Doctor <scott at scottdoctor.com> a ?crit :
> > A trick that works great most of the time with ODS is when exporting to > CSV select the option to quote all fields. One problem with CSV is that > many exports quote strings but not numbers. If everything is quoted then it > is much simpler to process. But would need at least several options on the > import: > > 1) what is the separator token (i.e. is it a comma, or a period, or a > semicolon,...) > > 2) what is the decimal token (i.e. is it a period, comma, other,...) > > 3) Should quoted strings keep the quotes or strip the quote characters > during processing > > 4) What is the escape sequence for embedding a quote character within a > quoted string > > 5) using single or double quote character as the quote token. > > As you can see the number of permutations grows very fast to accommodate > the wide variety of ways common programs handle CSV exports. > > On 7/30/2015 11:28 AM, Bernardo Sulzbach wrote: > > > I can remember two times when my life would have been easier if I > > could throw big .ods into sqlite3 dbs. > I would like something that works, actually I never could use the import csv from sqlite, I had to build my own, like probably many others. Why is it not possible to have a solution directly in sqlite?
