SQL news and developer summaries

A persistent MySQL bug, identified in 2005, caused triggers to fail during cascading foreign key operations. After 20 years of community discussion and controversy regarding database integrity, the issue has finally been resolved as part of WL#17024, enabling triggers on referenced tables during cascade events.

The US Library of Congress recommends SQLite as a top-tier storage format for datasets. It joins XML, JSON, and CSV due to its high level of transparency, self-documentation, and low dependency requirements, ensuring long-term digital preservation and archival accessibility for critical datasets.

This guide outlines six SQL patterns for detecting transaction fraud, including velocity checks, geographic impossibility, amount anomalies, merchant behavior analysis, off-hours tracking, and the use of window functions for rapid iteration. These techniques help identify suspicious activity in financial or benefit-related datasets, emphasizing that SQL remains the most effective tool for practical, scalable fraud detection.

SQL and relational databases often suffer from concurrency bugs like atomicity issues, TOCTOU, and deadlocks. While techniques like transactions and explicit locking solve these problems, they increase complexity. The author advocates for a database system that prioritizes correctness by default, inspired by Rust’s fearless concurrency model, to ensure safer data handling.