Leo Hemsted 3739c573ea fix null check in constraint ...

There are two fun quirks of postgres/sql that we need to work around:
* any `x = y` where x or y is NULL returns NULL, rather than false.
* check constraints accept NULL or true values as good.

so, the check `postage in ('first', 'second')` returns `null` rather
than `false` when postage is null itself. This surprisingly passes the
check constraint. To get around this, we have to add an explicit not
null check as well.

2018-09-25 16:10:26 +01:00

70 KiB

Raw Blame History

View Raw