<?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/d2bfec689fb742cba5a40c21138ca43d&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/d2bfec689fb742cba5a40c21138ca43d-ed03d45422ec08e0.gif</thumbnail_url><duration>116.297</duration><title>Improving Immutable Relations With Triggers</title><description>This Loom explains a PR update to make arity and isRelation stable and more robust across instances. After feedback from Devin that “cheating on immutable” was not a great idea, the author set both arity and isRelation as stable, non-null ordinary columns maintained by triggers that compute values before insert and propagate changes after insert when literal content changes. The author also improved addConcept so it represents proper source and schema by adding pairRelationTripleSchema and verifying isRelation is correct. Finally, a change to stepDef was made to record the IDs of the inserted, absolute concept.</description></oembed>