Any particular reason why the shell '.import' command cannot interpret || as a NULL for the field? Does || have another use/interpretation?
Just seems a shame that the standard bulk input mechanism cannot cope directly with NULLs. Best regards On Wed, Mar 16, 2016 at 9:13 AM, Simon Slavin <slavins at bigfraud.org> wrote: > > On 16 Mar 2016, at 9:02am, Simon Slavin <slavins at bigfraud.org> wrote: > > > No. Use one of these two methods. > > I'm sorry. I read your 'import' but I thought you meant using INSERT. If > you are using the shell's ".import" command then Clemens is right. You are > importing from a text file, and there is no way to put a NULL in a text > file. After your import you should do something like > > UPDATE t SET b=NULL WHERE b='NULL'; > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
