Only reliable Data: Protecting Database Integrity with Eva Nanyonga
summary
Shows a concrete account-creation API built with Django and Django REST Framework, exercised from Postman against PostgreSQL, where an attempted email send raises a SMTP connection refused error and naive code creates duplicate users (database count jumps from 5 to 11). Wrapping perform_create in a transaction.atomic context (or using the @transaction.atomic decorator) rolls back partial writes. Demonstrates debugging steps, error typing, and that atomic blocks prevent inconsistent ledger state.
AI-written summary · about
chapters (6)
- 0:00Reliable database data
- 1:50Atomicity for integrity
- 3:15Atomic transactions demo
- 10:12Django transaction API
- 12:01Critical atomic use cases
- 15:14Summary & Q&A
related talks
28mPessimism, optimism, realism and Django database concurrency
48mAuto-generating an API using PostgreSQL, Django, and Django REST Framework
01h 06mEffective Django
33mPeaceful Django Migrations with Efe Öge
21mBuilding maintainable Django projects: the difficult teenage years
22mDjango with PostgreSQL superpowers
24mDjango as a Database Documentation Tool: The Hidden Power... with Ryan Cheley
26mMaking Django Really, Really, Ridiculously Secure (CW)