<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/5aef4295495b4577b436b359246febe4&quot; frameborder=&quot;0&quot; width=&quot;1552&quot; height=&quot;1164&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1164</height><width>1552</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1164</thumbnail_height><thumbnail_width>1552</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5aef4295495b4577b436b359246febe4-631f581400c7828d.gif</thumbnail_url><duration>294.9</duration><title>Troubleshooting SQL queries with the omni_id extension</title><description>Do you prefer to read instead of watching? Here&apos;s a blog article: https://blog.omnigres.com/troubleshooting-sql-queries-with-omni-id
---

Hey 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.

Documentation: https://docs.omnigres.org/omni_id/identity_type/

Learn more about Omnigres: https://github.com/omnigres/omnigres</description></oembed>