Files
notifications-api/migrations/versions
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
..
2017-03-02 12:12:01 +00:00
2017-04-26 10:37:12 +01:00
2017-06-01 13:18:56 +01:00
2017-06-01 15:58:15 +01:00
2017-06-20 10:56:50 +01:00
2017-06-26 14:03:02 +01:00
2017-11-15 12:42:49 +00:00
2018-01-05 15:58:13 +00:00
2018-01-05 16:00:29 +00:00
2018-02-08 11:26:10 +00:00
2018-08-23 14:43:41 +01:00
2018-08-23 15:04:44 +01:00
2018-08-24 16:09:17 +01:00