Thanks for the report. Fixed on trunk, here:
https://www.sqlite.org/src/info/fc918f7d33
--
Joe Mistachkin
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Hello,
I've taken the time to investigate the problem: only the last
parameter is not correctly bound to NULL.
May I suggest a patch:
--- shell_.c 2014-06-15 14:22:39.0 +0200
+++ shell.c 2014-06-15 14:23:11.0 +0200
@@ -2553,7 +2553,7 @@
"filling the rest
gwenn, thanks for this. I did not understand what you saw, and then I
realized my shell exe was probably too old.
I downloaded the new exe and this solves the problem just fine!
thanks for your help.
gert
2014-06-02 19:03 GMT+02:00 gwenn :
> Hello,
> I doesn't fail for me (it may depend on the
Hello,
I doesn't fail for me (it may depend on the constraints on the target
table) but the behaviour is unexpected:
$ echo "1|test
> " > empty.csv
$ sqlite3
SQLite version 3.8.4.3 2014-04-03 16:53:12
sqlite> create table test(opt text, data text not null);
sqlite> .import empty.csv test
empty.csv
All,
I received 100.000 UTF-8 files (average size 50kb) "ready for import" in
an SQLite db.
90% of them go fine, but some files have an empty line at the very end of
the fine (so an extra EOL before the EOF).
Of course, the import fails... Is there an easy way to get rid of that
extra empty line
5 matches
Mail list logo