Roger Binns wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09/13/2010 04:06 PM, BareFeetWare wrote:
>> All this talk of replacing multiple commas with pipes, then replacing pipes
>> and so on, though clever and helpful is problematic, cumbersome and even
>> comical for a mature product like SQLite.
>
> SQLite is a SQL library and does an excellent job of that.
>
> Numerous tools are built on top of that library. One example is a shell
> which can be used for interaction with a SQLite database, but is not
> formally specified, supported nor developed to the same degree as the
> library. You are not required to use the shell, and there are numerous
> alternatives.
>
> See also:
>
> http://www.sqlite.org/src/rptview?rn=5
>
> It is fairly easy to write your own as appropriate. Some self horn tooting:
>
> http://apidoc.apsw.googlecode.com/hg/shell.html
>
> Roger
Roger --
I Agree -- sqlite3 is NOT the sqlite DB engine.
Thanks for the links. I will try out your sqlite shell.
As to Code_Defect# c25aab7e7e ...
I have never had any problems importing simple pipe-delimited .txt
files into sqlite DBs via the sqlite3 shell.
Maybe instead of 'fixing' sqlite3 .CSV imports, you could simply
change the description of the .import command to
.import - import simple delimited text files.
CSV IO is a monster. Even MS Excel doesn't export proper CSVs
and it sure as hell can't import them( quoted strings that look
like numbers ALWAYS become numbers in Excel).
Besides, pre-filtering raw text files before finally executing
`sqlite3 ... ".import ..."` is the 'UNIX way' !
My $0.02 ...
-- kjh
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
