diff options
| author | drh <drh@noemail.net> | 2002-05-26 20:54:33 +0000 |
|---|---|---|
| committer | drh <drh@noemail.net> | 2002-05-26 20:54:33 +0000 |
| commit | f5905aa7be3a44909f108583ad07a54eeb60f37c (patch) | |
| tree | 93fb95609d340f184aec2b23561de1d2dbbd3bcd /src/trigger.c | |
| parent | 195e6967fb489401471c7ab99e3c4042d07347f4 (diff) | |
| download | sqlite-f5905aa7be3a44909f108583ad07a54eeb60f37c.tar.gz sqlite-f5905aa7be3a44909f108583ad07a54eeb60f37c.zip | |
NULL values are distinct. A comparison involving a NULL is always false.
Operations on a NULL value yield a NULL result. This change makes SQLite
operate more like the SQL spec, but it may break existing applications that
assumed the old behavior. All the old tests pass but we still need to add
new tests to better verify the new behavior. Fix for ticket #44. (CVS 589)
FossilOrigin-Name: 9051173742f1b0e15a809d12a0c9c98fd2c4614d
Diffstat (limited to 'src/trigger.c')
| -rw-r--r-- | src/trigger.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/trigger.c b/src/trigger.c index 48e7ecf79..82ba258a0 100644 --- a/src/trigger.c +++ b/src/trigger.c @@ -587,7 +587,7 @@ int sqliteCodeRowTrigger( sqliteExprDelete(whenExpr); return 1; } - sqliteExprIfFalse(pParse, whenExpr, endTrigger); + sqliteExprIfFalse(pParse, whenExpr, endTrigger, 1); sqliteExprDelete(whenExpr); codeTriggerProgram(pParse, pTrigger->step_list, orconf); |