> It’s the worst of a leaky abstraction, and like 3x the conceptual overhead. I really think you hit the nail on the head with this sentence. For example, anot

> It’s the worst of a leaky abstraction, and like 3x the conceptual overhead. I really think you hit the nail on the head with this sentence. For example, another commenter said "But the same SQL fanboys who believe every developer ought to memorize tri-state truth tables..." Yes, I think it's fine to argue that the boolean logic with respect to NULL in SQL is a pain in the ass. But ORMs certainly don't hide that from you! The ways DBs treat nulls is a fundamental part of nearly all RDBMSes - if you don't understand that, you're (eventually) going to have a bad time. All ORMs really do is make it harder to understand when you may need to take special null logic into account.