4 ms·

SQL null is not like the null of programming languages, it behaves more like "unknown" than "blank". For instance, null != null. Arithmetic on null values is al

SQL null is not like the null of programming languages, it behaves more like "unknown" than "blank". For instance, null != null. Arithmetic on null values is also well-defined so that 1 + null = null. I'm not convinced that implicit nullability is a good idea, either in SQL or in newly designed languages. I don't see the connection between implicit nullability and SoA. If you have a link to some example, that would be interesting to read.

henrydark 4y ago
I'm not convinced so either, just that it doesn't not make sense. As for SoA, I'm thinking of two relatively new formats and applications that have default nullable types, are SoA, and are specifically targeting memory intensive applications: apache arrow and duckdb, both seeing some success and well deserved hype