The following might be options (compile time, config file, set manually;
I don't care), but they should be available...
1) import with strict typing. If I create a table with 3 numeric (real.
integer, whatever) fields, then a CSV file containing...
2.345, 42, 27.7
should import as 3 numbers, not as 3 character strings
2) import adjacent commas in a CSV file as NULL, not as a zero-length
string. As for the argument that SQLite can't read my mind...
a) if it can't read my mind, I need to be able to tell it what I want
b) why would I want a "zero-length string" to behave any differently
from NULL?
c) why on earth would I want a "zero-length string" in an *INTEGER*
or *REAL* field??? That is a totally insane default.
--
Walter Dnes <[email protected]>
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
