4 ms·
Not that a class needs to be a primitive, but that patterns like inheritance should be reusable in some way through templating or the like. And the inability t
by Pxtl 10y ago
Not that a class needs to be a primitive, but that patterns like inheritance should be reusable in some way through templating or the like.
And the inability to pull down a graph as a single operation is the perfect example of sql's limitations.
Relational model is great right? Right. So why throw it out the window and give me a glorified excel spreadsheet as a result set? If I want to pull down a thing and it's related subthings in a single operation, I have to join which is wasteful in that case. This actualy hamstrings ORMs.
- ianamartin 10y agoI don't think you understand relational databases. I wouldn't hit you with an actual brick, but if I worked with you, I'd certainly nerf dart you on a regular basis.
- Pxtl 10y agoI understand relational databases just fine. I still have no interest in the Stockholm syndrome of defending a platform where a = a can evaluate to something equivalent to False, regardless of the theoretical underpinnings of three-valued logic. There are so many pain points in SQL that are defended because theory.