all makes sense for the cloud - you'd be horrified at how some of my internal IT web apps follow none of this, running on SQL express on a 15 year old on-premise server 😂
2026-04-10 06:52:04
3
Pabloescobarito36 :
The mistake 4 is not always true. Dépeint on the dbms the optimiser can transform the subquery into a regular join
2026-04-09 21:43:18
1
cârcel :
you lost me from slide "Mistake #4"... joins do exactly what you point out in "Mistake #1". Joins are executed: for each row on the left, find the corresponding ones on the right (iteration over entire table) and associate them. The sub-select does the same thing.
Here is another advice:
❌ - joins (especially between big tables) when you don't need data from joined table, but only to apply some filters
✅ - use 'where exists (select 1 from ... where join_clause_here)', mysql will stop and return true at first record found (returns earlier then joins). I've optimized some queries at x10 speed with this
2026-05-08 19:12:00
0
Dj Kad 🇮🇹 :
also cache can reduce drastically response time
2026-04-08 21:36:05
3
_ :
haven't they created yet a gui and a safe gui instead of having to always use commands? and wrong command all is gone without confirmation nor ctrl z
2026-04-07 15:02:43
1
Motion troupper :
unless the index is built on YEAR(created at)
2026-04-08 07:08:56
2
zippo :
Who the hell filters with having?
2026-04-08 18:32:53
0
mouse_ :
then what should I use if I have to get every column of user with id 1?😭😭😭
2026-04-07 14:49:09
1
herheliuk :
enable wal
2026-04-08 08:54:15
1
To see more videos from user @poopooundkakaland, please go to the Tikwm
homepage.