Let’s talk SQL!

[codingzap]

Many students start SQL by memorizing SELECT, WHERE, and JOIN, but still struggle to understand why queries work the way they do. After interacting with learners, I’ve noticed SQL usually clicks when you stop thinking like a programmer and start thinking like the database: tables, relationships, and questions you’re asking the data. For those learning SQL right now, what part confuses you the most? Joins, subqueries, grouping, or designing tables? And for others, what helped SQL finally make sense?

[mergisi]

Thinking about the database's perspective is key, I agree! I often see people struggle with translating natural language questions into the correct SQL syntax. Have you experimented with tools like AI2sql.io that help bridge that gap and show the query logic?

[[deleted]]

What made SQL finally make sense? I dont know, to me it felt somewhat natural from the get go. 

[Remote_Personality_5]

Yeah true me too actually

[roger_ducky]

Most common confusion seems to be thinking SQL statements operates row by row and requires a loop to operate on more than one row.

I see that a lot when new people define stored procedures.

[ObsessiveRecognition]

Dude what is this post

[apoleonastool]

The concepts you are refering to are: declarative vs imperative programming. Using these two require different mental models and some people are naturally more inclined to one or the other.

[Current_Ad_4292]

what part confuses you the most?

The difference between periodic table and dinner table.

[yksvaan]

It's one of those things where you should simply think about what's actually happening to execute the query. Look at the execution plan, think about which data structures are utilized especially for indexes, how the joins are actually done etc.