3 ms·
What? > SQL was designed for reading and updating relational data. Data in tables that can be joined with relational intersections, unions and complements. Ob
by Pxtl 12y ago
What?
> SQL was designed for reading and updating relational data. Data in tables that can be joined with relational intersections, unions and complements.
Obviously. And it fails miserably at providing you with tools to reuse this code.
> This is your proverbial impedance mismatch. We have to "deal with it" without compromising the idiomatic strengths of either paradigm.
That's a cop-out. Purist functional programming languages provide namespaces, packaging systems, etc. even though nowhere in the academia of "lambda calculus" is stuff like that mentioned. At some point the rubber hits the road and you have to interface with your beautiful kernel of relational algebra, and you have to organize all that relational stuff.
Nowhere in Date and Darwin's work does it say that a relational set must be defined by a name. Why can't it be defined by a tree of namespaces? Or packages? Or anything other than simply a flat list of names?
At some point it's time to stop making excuses for this antediluvian system. SQL platforms make exceptions from the SQL spec for stupid things like bolting on a procedural scripting language, but never for smart things like better organization tools for code-reuse.