31–40 of 302 posts
Do people still write SQL?
Earlier quoted context omitted.
There was this professor of language who would say "Do you think the question ('are carpets furniture?') tells you something about the ambiguity of the word carpet, or do you think it tells you something about the ambiguity in the world?" Similarly, I think joins are "tough" not because of the way SQL expresses them but because the logical possibilities of merging data from multiple tables are varied.
There is no such thing as a domain-agnostic SQL database that holds up under this kind of semantic scrutiny. I don't think that there ever could be. If you are rolling a SQL schema for a home improvement contractor, it is extraordinarily unlikely that their specific business would expect any scenarios in which carpets are sometimes known as furniture. Having a bounded context to operate within is what makes SQL magic…
I was not proposing a SQL database of carpets, or furniture, as a thought experiment.
And then dump the queries via https://stackoverflow.com/questions/1412863/how-do-i-view-th... or https://www.linqpad.net/ ?
[0] - https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL...
https://heap.io/blog/postgresqls-powerful-new-join-type-late...
https://stackoverflow.com/questions/28550679/what-is-the-dif...
https://docs.snowflake.com/en/sql-reference/constructs/join-...
The TL;DR is that they allow you to reuse annotated and aggregated columns in an incredibly elegant way. Compared to OP's proposal, you still do need to start the query with what columns you want to come out at the end, and normal SQL weirdnesses still apply - but it's far, far, easier when writing massive analytics queries to see the flow of variables from one stage to another.
- https://github.com/RCHowell/Sift - https://github.com/RCHowell/Sift/blob/main/src/main/kotlin/c...
Do people still write SQL?
Do people still write SQL?
My thought is that joins are the tough part of the SQL learning curve, but I don't see much in here that reduces the complexity of joins.
There was this professor of language who would say "Do you think the question ('are carpets furniture?') tells you something about the ambiguity of the word carpet, or do you think it tells you something about the ambiguity in the world?" Similarly, I think joins are "tough" not because of the way SQL expresses them but because the logical possibilities of merging data from multiple tables are varied.