Hi, yes, this is expected. Note that you use the = - operator in WHERE maybenullcolumn = @value and NULL = NULL evaluates to false. This is SQL standard.
Martin [email protected] wrote: > Hello, > > In my usage of SQLite, I found a behavior that might be considered a > bug, but I would like others' input on it. > > Consider the following table with a single row, with one column > containing a null value: > > CREATE TABLE MyTable (id integer primary key autoincrement, label > char(255), maybenullcolumn integer); > INSERT INTO MyTable (label) VALUES ('Label'); > > If one tries to retrieve that row with the "IS NULL" syntax, it works > fine (the following statement returns 1): > SELECT COUNT(*) FROM MyTable WHERE maybenullcolumn IS NULL; > > ... but if one uses parameters, the statement returns 0: > SELECT COUNT(*) FROM MyTable WHERE maybenullcolumn = @value; > ... > sqlite3_bind_null(pStmt, 1); > > Is this expected? > > Thanks, > > Diego > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
