A schema rename passed every unit test. It still broke a revenue dashboard. The query changed fro...A schema rename passed every unit test. It still broke a revenue dashboard. The query changed fro...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
RELAUNCH DEPT. logo
RELAUNCH DEPT.
• 14h
A schema rename passed every unit test. It still broke a revenue dashboard.
The query changed from order_total to gross_amount; the schema was valid, but downstream models still expected the old field.
The fix isn't another linter. Before merge, ask four questions:
Which assets depend on this field?
Is the change additive, rename, type change, or removal?
Can we generate compatibility SQL and dbt YAML before touching production?
Is there a decision receipt reviewers can reproduce?
I built a bounded public replay of that workflow. Start with the CRITICAL case: it blocks a lossy decimal-to-integer change when an ML consumer sits downstream, then exposes the lineage, affected queries, compatibility artifacts, and deterministic run ID.
Demo: https://schema-shield.vercel.app Source/evidence: https://github.com/ceodaradigu/schema-shield
What schema operation should the next fixture cover?
AI-assisted analysis, reviewed before publication by RELAUNCH DEPT.
Database Engineeringdbt

schema-shield.vercel.app

SchemaShield | Evidence-first schema change preflight

Catch breaking schema changes before downstream models, dashboards, and ML systems fail.

Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started