SQLite allows NUL characters (ASCII 0x00, Unicode \u0000) in the middle of string values stored in the database. However, the use of NUL within strings can lead to surprising behaviors:
The length() SQL function only counts characters up through and excluding the first NUL.
The quote() SQL function only shows characters up through and excluding the first NUL.
The use of NUL characters in SQL text strings is not recommended.
Consider the following SQL:
CREATE TABLE t1( a INTEGER PRIMARY KEY, b TEXT ); INSERT INTO t1(a,b) VALUES(1, 'abc'||char(0)||'xyz'); SELECT a, b, length(b) FROM t1;
The SELECT statement above shows output of:
SELECT * FROM t1 WHERE b='abc';
Then no rows are returned. SQLite knows that the t1.b column actually holds a 7-character string, and the 7-character string 'abc'||char(0)||'xyz' is not equal to the 3-character string 'abc', and so no rows are returned. But a user might be easily confused by this because the CLI output seems to show that the string has only 3 characters. This seems like a bug. But it is how SQLite works.
If you CAST a string into a BLOB, then the entire length of the string is shown. For example:
SELECT a, CAST(b AS BLOB) FROM t1;
Gives this result:
In the BLOB output, you can clearly see the NUL character as the 4th character in the 7-character string.
Another, more automated, way to tell if a string value X contains embedded NUL characters is to use an expression like this:
If this expression returns a non-zero value N, then there exists an embedded NUL at the N-th character position. Thus to count the number fo rows that contain embedded NUL characters:
SELECT count(*) FROM t1 WHERE instr(b,char(0))>0;
The following example shows how to remove NUL character, and all text that follows, from a column of a table. So if you have a database file that contains embedded NULs and you would like to remove them, running UPDATE statements similar to the following might help:
UPDATE t1 SET b=substr(b,1,instr(b,char(0))) WHERE instr(b,char(0));