Re:Postgres 15 improves UNIQUE and NULL
by wongarsu on Monday July 11, 2022 @09:33AM
(#32055901)
Yeah, in hindsight the world would be a slightly better place if SQL didn't include NULL, but instead "UNKNOWN" and "NONE", with "NONE = NONE" being true, and "UNKNOWN = UNKNOWN" being unknown.
[ Parent
| on HN ]
Or have an Option (or Maybe) type. This is how modern programming languages solve the nil issue, I don't see a reason why a database couldn't take the same approach.
When would NONE show up and when would UNKNOWN show up?