Le jeudi 30 juillet 2015, Simon Slavin <slavins at bigfraud.org> a ?crit :
> > On 30 Jul 2015, at 7:48pm, Sylvain Pointeau <sylvain.pointeau at gmail.com > <javascript:;>> wrote: > > > really cool, but I would like to have a solution directly in the sqlite3 > > executable > > If you're talking about the SQLite shell tool then Excel import will never > be integrated into it. There's no way to know when Microsoft is going to > change or add to their file specification for Excel, and it would oblige > the SQLite development team to update the shell tool on an schedule only > Microsoft could predict. > > By the way, an earlier premise of this thread is incorrect. CSV is > perfectly standard and perfectly documented: > > <https://tools.ietf.org/html/rfc4180> > > The CSV importing part of the SQLite shell tool implements this very well. > > Simon. > No it does not implement the rule 5 correctly: Each field may or may not be enclosed in double quotes (however some programs, such as Microsoft Excel, do not use double quotes at all). If fields are not enclosed with double quotes, then double quotes may not appear inside the fields. Why sqlite keeps the quoted string in the database? Except of this, it would work well I would say
