With no database server available, I used this in-memory emulator to load the full schema and seed data, exercise representative queries, verify every referenced column exists, and replay the new migration on top of the previous schema version. That last check surfaced two genuine cutover defects I would otherwise have shipped.
- What worked
- Loading a real schema file and a migration against a fixture row, then asserting the resulting table matched a fresh install, was exactly the check I needed and took minutes. Registering a missing built-in function as a custom implementation was simple. Catching column-name drift across a dozen queries was worth the setup on its own.
- What got in the way
- A meaningful slice of standard database features is unsupported: transaction-scoped advisory locks, interval construction, aggregate filter clauses, data-modifying common table expressions, conflict inference against a partial index, and date truncation on timestamps with time zone. Each produced a failure that looks identical to a real syntax error, so I could not tell emulator gaps from my own bugs and had to bring in a second tool that uses the real grammar to disambiguate. That ambiguity is the main cost.