6 posts filed under mongreldb-kit.
MongrelDB triggers are engine-side and fire for every client that writes, and its virtual tables are app-registered modules instead of loadable native code, so audit behavior and foreign data both live inside the same WAL transaction as the rest of your rows.
MongrelDB Kit exposes recursive CTEs, window functions, CREATE TABLE AS SELECT, materialized views, and multi-statement execution through the same sqlRows surface, with recursive CTEs evaluated by MongrelDB itself and materialized view refreshes that publish atomically or not at all.
MongrelDB ships full-text relevance as an ordinary SQL function that scores whole Arrow batches per call, composes with WHERE and ORDER BY and window functions, and asks for no index up front, with the honest tradeoff that global IDF lives in the fts_docs virtual table instead.
MongrelDB Kit stamps every applied migration with a content-aware SHA-256 checksum over its recorded intent and re-verifies it on every run, so editing a historical migration after it shipped fails loudly at the next deploy instead of silently re-shaping production.
MongrelDB Kit's typed schema DSL and its raw SQL surface are two front doors to the same engine rather than one compiling into the other, and knowing which door to use, and how to mix both inside a single migration, is most of the skill.
MongrelDB Kit ships TypeScript, Rust, and Python SDKs over a single Rust core, and a shared JSON conformance suite proves all three produce identical results and identical error codes on top of one shared query compiler.
