Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
19 results across 1 active filter
Page 1 of 1
Defines Django transaction nesting, exception boundaries, and post-commit work without promising durability.
Explains object identity, tracked changes, flush ordering, and the limits of session-level caching.
Chooses relationship loading from cardinality, query count, result size, and hidden-I/O boundaries.
Chooses atomic database expressions, row locks, and constraints from the invariant being protected.
Connects pool limits to process topology, transaction duration, database capacity, and queueing evidence.
Separates stale checkout protection, connection aging, pool waits, statement timeouts, and uncertain transactions.
Defines one explicit SQLAlchemy session and transaction owner for each request, job, thread, or async task.
Finds repeated relationship queries and fixes the data shape without introducing a larger query problem.
Connects one slow Python request to generated SQL, representative parameters, database plans, and measured validation.
Separates SQLAlchemy connectivity, checked-out database resources, ORM state, and transaction ownership.
Makes AsyncSession transaction ownership and every database I/O point explicit.
Connects SQLAlchemy object states to flush, commit, close, serialization, and later attribute access.
Separates SQL synchronization from transaction completion and explains recovery after database errors.
Explains lazy query construction, evaluation triggers, result caching, and repeated-query surprises.
Aligns selected database data with an API read model and avoids unnecessary ORM state.
Chooses Django relationship loading from relationship shape, result cardinality, and measured query behavior.
Chooses a SQLAlchemy abstraction from the work's shape instead of performance slogans.
Aligns SQLAlchemy transactions with business operations and uses savepoints without inventing independent commits.
Treats Alembic autogeneration as a candidate schema diff that still needs semantic and operational review.