Comments added to the SQL channel I think we need to review/action

Alessandro:
Scotland Week 1 retro points:

Add a few lines on dealing with multiple lines and statement closure in PSQL prompt.
Explicitly mention use of single quotes for strings
Add table explainer for different terms / types
Explicitly mention switches between PSQL prompt and shell
Commands should be documented under "useful Commands" section. Currently \dt,\d,\q commands are spread all over the page.
Discussion - should we use a GUI for visualisation instead of just the command line?

Daniel:
Just following up on Scotland retro as I was teaching in the morning but couldn’t join the retro.This was my first time teaching the SQL module. I was surprised the module focuses so heavily on the command line. I use postgres a lot and I literally never use psql except for esoteric requirements like listing all functions in a schema.Part of what makes databases great to teach is that you can actually visualise what’s going on so it seemed strange to avoid GUIs. In the end I told students to install Beekeeper which is a cross-platform DB GUI.There were a few quirks in the syllabus that I think could benefit from review and iteration. Things like using varchar when in practise you’re just as well using text , use of camel case for column names in diagrams (this will trip learners up as they’ll need to quote identifiers). There’s quite a lot of verbosity in how things are explained (which is a great place to start!) but with a bit of iteration I think we could do a better job of pulling out the key concepts in a more concise way.I spent a while talking about modelling a schema, using Google Sheets to illustrate, before we jumped into any syntax. We talked about whether a booking should reference a customer, or a customer should reference a booking to highlight one-to-many relationships. I think it would probably be good to start the lesson with a focus away from syntax and perhaps modelling exercises that can be completed without coding.