3 ms·

AFAIK MySQL and Oracle have the same flaws.

• dragonwriter 5y ago
  MySQL and Oracle also lack standard boolean support while allowing true boolean values as results in certain positions, AFAIK, yes, although some versions of MySQL use “Boolean” as an alias for tinyint(1) and even more support TRUE and FALSE (without quotes) as aliases for 1 and 0, which confuses the issue a bit. SQLite has a similar problem, averts the practical because it doesn't use booleans natively internally in which they apply, instead natively using 0 and 1 (with TRUE and FALSE as aliases) and then converting to boolean in the narrow set of boolean contexts. This means that can use COALESCE as described (and, generally, SQLite will behave as you would expect with real Boolean support, even though it doesn't actually have it.) DB2, from what I can find, supports BOOLEAN from v11.1. In any case, the problem here is not a standard SQL problem, even if it is a problem of several popular SQL implementations.