On Mon, Feb 15, 2010 at 07:31:43PM +0000, Simon Slavin scratched on the wall: > > So the command-line tool cannot correctly read the CSV files > it output itself ? Okay, that's messed up. Something should be done.
Yes, and always will be. Different version of Excel have similar issues. The topic of what the "correct" format of a CSV file has been beaten to death on this list in the past. I suggest that if you have the need to import a large number of specific CSV files, you write your own importer and/or exporter, either via your own code that matches your needs or by using one of the more popular Perl or Python parsers. The simple fact is that everyone has a different idea of what makes up "proper" CSV, so the format is pretty worthless for general use. Now, I know that sounds funny, but go read the archives. If you think CSV is simple, I invite you to have a look at the massive Python module and all the odd special-case bits it has. I suspect the SQLite team has just dismissed the whole issue out of hand, and personally I agree with that. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
