{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/5aef4295495b4577b436b359246febe4\" frameborder=\"0\" width=\"1552\" height=\"1164\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1164,"width":1552,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1164,"thumbnail_width":1552,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/5aef4295495b4577b436b359246febe4-631f581400c7828d.gif","duration":294.9,"title":"Troubleshooting SQL queries with the omni_id extension","description":"Do you prefer to read instead of watching? Here's a blog article: https://blog.omnigres.com/troubleshooting-sql-queries-with-omni-id\n---\n\nHey there! In this video, I walk you through a scenario where we encounter unexpected results in a SQL query. We dig into the issue of mismatched identity types causing data discrepancies and how the new omni_id extension helps us define specific identity types for each entity, ensuring data accuracy.\n\nDocumentation: https://docs.omnigres.org/omni_id/identity_type/\n\nLearn more about Omnigres: https://github.com/omnigres/omnigres"}