Ooh, SQL, I forgot about that one. I sure did have problems with SQL when I first tried to wrap my head around it. Maybe I'll have to exclude it from the set of "algorithmic languages", if I'm to preserve my original assertion.
(Thankfully I had a SQL jock who sat nearby, about the same time I had to begin using it for more than just one-line queries. The trick, I finally concluded, is to ~start~ with the FROM clause. Design that first, and maybe GROUP BY next, and everything else seems easy enough after that.) --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* We must picture Hell as a state where everyone is perpetually concerned about his own dignity and advancement, where everyone has a grievance, and where eveyone lives the deadly serious passions of envy, self-importance, and resentment. -C S Lewis, preface to _The Screwtape Letters_ */ -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, April 7, 2020 18:50 True. Which is why many (experienced?) programmers, at least at first, have some problems with SQL and thinking in "sets". --- On Tue, Apr 7, 2020 at 10:07 AM Nightwatch RenBand wrote: > Best thing I learned: Virtually all programs come down to Input, Process, > Output. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
