{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/c85ab554ec224f89af3f4b06f8c2c40d\" frameborder=\"0\" width=\"3024\" height=\"2268\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":2268,"width":3024,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":2268,"thumbnail_width":3024,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/c85ab554ec224f89af3f4b06f8c2c40d-6f423e357d8110fe.gif","duration":50.162,"title":"Using dbdiff to validate database migrations","description":"This Loom explains applying dbdiff to a set of pull requests and resolving differences caused by unchecked comments. The author notes that differences included comments not kept in check, and after updating them they rerun dbdiff to confirm the migration results. The process will create another version, apply the migration, and re-check the difference. In the author’s case, a pgcron remains because it is part of this PR but not another, while in most cases it should report that nothing is left and everything is fine."}