<?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/9162523288284401b9679c7b743a726c&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9162523288284401b9679c7b743a726c-5d916a5793d07150.gif</thumbnail_url><duration>138.451</duration><title>Adding Content Type for Absurd Functions</title><description>This Loom explains a schema and type change that adds a content type column to the content and document tables. The author notes the main update is introducing a non-null character varying field with a default of text plain, and that this propagates through view logic, local input types, and functions, including assumptions about ROAM being application ROAM.json (with possible text ROAM plus markdown as an alternative). They also describe adjusting queries and migration and DB types to include the content type. Finally, they mention updating tests, with attention to the “absurd node as content with embedding” behaving consistently.</description></oembed>