On Wed, 01 Dec 2004 16:35:48 -0500, you wrote: >I have lately noticed a need for an "IS" operator in SQLite. >IS would work just like "=" for most things. The difference >is that "IS" would compares NULLs as equals. There would, >of course, need to be a corresponding "IS NOT" operator. > >You can already us the IS operator with a right-hand side >of NULL. For example: "x IS NULL" or "x IS NOT NULL". What >I am proposing is to expand IS so that the right-hand side >can be an arbitrary expression. Like this: "x IS 5" or >"x IS NOT y". > >The motivation for this change is so that one can compile >statements that use "?" as the right-hand side of IS and >then insert NULL or a value as appropriate. > >Thoughts?
Sounds good, it would aid in the bindings a lot in those cases you mentioned. Without it, you would need to alter the sql statement instead of having a simple IF statement. I guess you would bind NULL with the sqlite3_bind_null. Speaking of bindings, is there any chance of allowing the '?' use in a create table statement as well? For binding of default values of a particular column. Thanks Randall Fox
