Database news and engineering 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 author argues that Object-Relational Mappers (ORMs) often cause more problems than they solve due to issues like attribute creep, complex foreign key joins, and the Object-Relational Impedance Mismatch. Instead of relying on ORMs for query generation, the author advocates for mastering SQL and treating the database as an API-driven data type.

The article strongly advocates for migrating from MySQL to MariaDB due to the deteriorating state of the former under Oracle's stewardship. By 2026, MySQL showed significant declines in git commits, limited bug tracking transparency, and a shift toward closed-door development. The author highlights technical regressions, performance degradation in newer versions, and a lack of new features in long-term support releases like MySQL 8.4. In contrast, MariaDB maintains a transparent, community-driven development model. Security concerns are also emphasized, noting that MySQL published significantly more CVEs with less disclosure compared to MariaDB. For users seeking to maintain software sovereignty and better performance, the author recommends MariaDB as a compatible, truly open-source alternative that provides an easy migration path for classic LAMP stacks and custom applications.

The article proposes using SQLite instead of Postgres for durable workflow execution, particularly for AI agents. By utilizing a local database file combined with Litestream for S3 backups, developers can achieve durable state management without complex infrastructure. This approach offers cost-effective, simple, and fault-isolated solutions, though Postgres remains better for high-availability requirements.

A recent security scan of 198 iOS apps revealed that 196 of them have exposed data, highlighting significant vulnerabilities in the mobile ecosystem. Major applications including Chat & Ask AI, GenZArt, and YPT - Study Group account for hundreds of millions of exposed records and files. This public registry showcases the scale of data exposure across various categories ranging from AI tools to educational games.

SQLite strict tables, introduced in version 3.37.0, enforce rigid data typing by preventing invalid type insertions and bogus column declarations. While strict tables add validation overhead and require table recreation for migration, they improve data integrity and prevent subtle bugs caused by SQLite's default flexible typing, despite the official advocacy for flexible schemas.

A database migration caused significant replication lag on May 12, 2026, leading to delayed Code Scanning, notifications, and webhooks processing. The issue, which lasted several hours, was resolved by scaling up processing workers. Future measures include creating dedicated worker pools for high-usage queues to maintain system stability and performance.

F3 is a next-generation open-source columnar data file format designed for efficiency, extensibility, and interoperability. It addresses layout limitations in formats like Parquet by embedding Wasm decoders within files, ensuring future-proof compatibility and platform-agnostic performance. The project provides a research prototype and API for developers, enabling adaptable data encoding schemes for evolving analytics workloads.

Many development teams prematurely adopt complex architectures, adding unnecessary databases like Redis, Elasticsearch, or MongoDB. Postgres is often sufficient for most use cases, offering robust features for caching, queues, search, and analytics. Prioritizing simplicity reduces operational overhead, maintenance burdens, and costs, allowing startups to focus on innovation until actual scale necessitates more specialized solutions.

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.

Using random UUID4 as primary keys in SQLite leads to significant performance degradation due to B-tree rebalancing and increased paging. Performance testing reveals that UUID4 inserts are 10-12 times slower than integer primary keys. Switching to time-ordered UUID7 effectively mitigates these issues, bringing performance near baseline levels despite the larger byte size of UUIDs.

PgDog is an open-source proxy project designed to make Postgres horizontally scalable, supporting over 1 million queries per second and 100 TB+ datasets. Founded by experienced infrastructure engineers backed by $5.5M in funding, it aims to eliminate scaling challenges for Postgres while providing flexible deployment options across cloud and on-prem environments.

The surge in demand for High-Bandwidth Memory (HBM) in AI data centers has created a severe global memory shortage. As memory manufacturers prioritize lucrative HBM over standard DRAM for smartphones and PCs, consumer electronics prices are spiking. This supply squeeze threatens the affordability of entry-level smartphones, reversing decades of technological democratization for the world's poorest populations.

This article explores unconventional optimization techniques for PostgreSQL to improve performance and reduce storage costs. Key strategies include using constraint_exclusion to skip unnecessary table scans, leveraging function-based indexes on virtual generated columns for lower cardinality data, and enforcing uniqueness on large values using exclusion constraints with Hash indexes.

DuckDB is a rapidly adopted, high-performance, in-process analytical SQL database designed for efficiency. Unlike server-based engines, it runs within the client application, avoiding network and serialization overhead. This analysis details its front-end architecture—covering parsing, binding, cost-based optimization, physical planning, and storage layer—explaining how it enables lightning-fast queries on formats like Parquet, CSV, and internal binary files.

pg_durable is a PostgreSQL extension that enables durable, fault-tolerant workflow execution directly within the database. By using a SQL-native DSL for checkpointing steps, it eliminates the need for external queues, workers, or cron jobs, allowing developers to build robust data and AI pipelines with automatic recovery from system failures and crashes.

This article challenges the 'use the right tool for the right job' mantra that often leads developers to manage multiple specialized databases (Elasticsearch, Pinecone, Redis, etc.). Such sprawl creates technical debt, complex security models, and high operational costs. Instead, the author advocates for using PostgreSQL as a unified platform. Innovations like pgvector (vector search), TimeScaleDB (time-series), and pg_textsearch (BM25 search) allow Postgres to match specialized tools' performance using similar algorithms. This simplification is especially critical in the AI era, where maintaining consistent data for agents is easier within a single, atomic environment. The post concludes that 99% of companies can achieve their goals with Postgres alone, reducing architecture fragmentation and potential failure points.

Codex is causing excessive disk write volume, estimated at 640 TB/year, due to verbose SQLite feedback logs set to TRACE level. This significantly impacts SSD longevity. The issue stems from default logging of high-frequency dependency events and telemetry. Proposed fixes include filtering TRACE logs, capping log size, and better managing payload storage to reduce I/O.

In this technical narrative, Leónidas Neftalí González Campos recounts a significant optimization challenge involving a REST API built with C# and the ABP framework. The issue centered on a 'Users list' endpoint that appeared to crash but was actually just extremely inefficient, taking over five minutes to complete bulk operations. The root cause was a '2-year-old hotfix' where developers used a foreach loop to await individual database inserts one by one. By bypassing the outdated ABP repository and directly implementing Entity Framework Core's AddRange and SaveChangesAsync methods, the author reduced execution time from five minutes to 300 milliseconds. The story highlights the dangers of technical debt and a 'feature factory' management culture that prioritizes speed over quality, emphasizing that significant gains often come from removing suboptimal practices rather than complex innovations.

Email validation is fraught with legacy issues and misconceptions. Instead of relying on complex, unreliable regex that often breaks valid cases like international characters, subaddressing, or unique domain formats, prioritize verification. Simply send a verification email to confirm the address is functional and owned by the user, while implementing case-insensitive storage for consistency.