Videos / Web Dev

Episode 8 of 16 · Web development, end to end

Postgres with Prisma or Drizzle: relations, and the queries an ORM hides

Chapters

1. Which database, still0:00
2. The shape at the door0:17
3. Four refusals in a row0:34
4. One to many, and the pair0:50
5. What you want, not how1:07
6. The last line of defence1:24
7. One fact, two answers1:42
8. One value per cell1:59
9. The whole key, or out2:16
10. Nothing but the key2:30
11. One sentence, three forms2:49
12. Two copies kept on purpose3:05
13. Both writes, or none3:21
14. The four letters3:38
15. Three ways a read lies3:57
16. Four levels, one default4:16
17. What the default permits4:35
18. Three ways to stop losing it4:54
19. One file, two outputs5:11
20. The model, written out5:29
21. Generate, then fail early5:45
22. Two ergonomics, one idea6:00
23. The type follows the query6:17
24. What you did not buy6:33
25. Numbered, and in order6:49
26. Both versions, at once7:07
27. Expand, backfill, contract7:23
28. A rename is two deploys7:41
29. The lock nobody expected7:58
30. Backfill in batches8:16
31. One query, then N more8:35
32. The cost is the waiting8:52
33. Ask for it up front9:08
34. Turn the query log on9:24
35. Read the plan inside out9:41
36. The index nobody added9:58
37. The whole thing10:18

Postgres with Prisma or Drizzle: relations, and the queries an ORM hides. Every new project asks the same question. Which database? For almost everything with users, orders, and things that belong to other things, the answer is still a relational one. Po

Mark as watchedSaved in this browser only.