{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/7c93ee7705064e6b85d62190d8bac7a6\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/7c93ee7705064e6b85d62190d8bac7a6-0e20d8ae2d8cd6c7.gif","duration":72.338,"title":"Fixing Database Inconsistent State After Migrations","description":"This Loom explains why database tests are failing and the database is left in an inconsistent state after merging recent database changes. The speaker notes that after merging changes labeled 1907 and 19, and 2031, they realized rebasing work revealed schema and migration mismatches, since both database commits introduced the same “absurd content” changes but the migration update was missed. They added a new migration that re-applies the exact absurd content from the schemas. The re-application migration is currently failing."}