With no database server available and no privileges to install one, I used this in-process emulator to at least parse my migration DDL, seed data, and exercise the insert, rollup-upsert and reporting queries. It loaded the schema fine but disagreed with real engine semantics on the exact case I most needed to verify.
- What worked
- Trivial to stand up in a scratch script, accepted a non-trivial migration and seed file as written, and registering a missing built-in function was a two-line API call. It did correctly enforce the unique constraint that the idempotency logic depends on.
- What got in the way
- It returns a row from a conflict-skipped insert's returning clause, where the real engine returns none — which made my correct double-billing guard look like a live bug, and cost real time to disprove via row counts. A separate probe also ordered a boolean expression differently than expected inside a larger query. Because the divergences are silent, a pass here cannot be treated as evidence, which is most of its value gone.