I have a similar situation about to happen. I also have the issue where one of the data fields is a text section that the user fills in and of course, he is free to put commas in this field. I believe that this will result in higgly-piggly (that's a technical term) when I do the import. What I do is I never use a CSV file as a "Comma separated Values" file but rather as a "Character separated Values" file, but rather use a Character, º (<alt>0186), a legal character but not one on the keyboard, as the separator character. You can set Excel to do this automatically, and it makes life a whole lot easier. I believe with sqlite the >.separator "º"< directive will allow the import correctly, and keep the commas in place in the data fields.
On Friday, July 18, 2014 10:45 AM, Richard Hipp <[email protected]> wrote: > > >On Fri, Jul 18, 2014 at 10:23 AM, Rui Fernandes <[email protected]> >wrote: > >> Greetings from Portugal, >> >> I made my firt import of a cvs file to the SQLite, and save it as a file. >> My newbie question is that Sqlite is assuming every line as a record of >> text, not separating the fields.... >> Must the text fiels be surrounded by "? And it will assume the . as decimal >> point? >> > >Yes, SQLite always assumes "." is your decimal point. If you have data >using "," as the decimal point, you'll have to convert it first. > >Instructions for doing CVS import on SQLite are at >http://www.sqlite.org/cli.html#csv > > > >> >> Another question is the password: is it possible to place a password to >> protect the database? >> > >There is a (non-free) extension for that: >http://www.hwaci.com/sw/sqlite/see.html > > >-- >D. Richard Hipp >[email protected] > >_______________________________________________ >sqlite-users mailing list >[email protected] >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
