Keep Batch Deletes Inside the Persistence Boundary
Repair a batch deletion path that depended on a read projection by loading persistence models directly, validating the full batch, and returning the real transaction result.
9 articles
Repair a batch deletion path that depended on a read projection by loading persistence models directly, validating the full batch, and returning the real transaction result.
Repair a metric labelled today that included the previous day by defining one local-day interval, isolating headline parameters, and reconciling the total with its detail population.
Repair a workflow report that advances too early by filtering invalid events, normalizing legacy stages, recovering from business evidence, and recording milestones only when transitions occur.
Turn an Oracle change list into a fail-closed synchronization program with target identity checks, full preflight validation, conditional DDL, business-key MERGE, and repeat-run proof.
Trace a valid database rejection back to stale derived allocation counters, repair the data under row locks and version checks, and translate the error only after rollback is guaranteed.
Diagnose primary-key collisions caused by sequence drift after an Oracle migration, align sequences forward during a verified write freeze, and prove recovery with complete transactions.
Trace an HTTP 200 empty response to an Oracle invalid-identifier error, replace legacy WM_CONCAT calls with deterministic LISTAGG, and verify source, build, artifact, and overflow boundaries.
How moving selective business filters ahead of window functions and dependent aggregates cut a paginated Oracle query from 27.49 seconds to about 1.40 seconds.
Replacing full-detail loading with database aggregation after a production dashboard timed out and left every counter at its initial zero.