video1.0<iframe src="https://www.loom.com/embed/2981055089e1450ba015badc417b26c6" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/2981055089e1450ba015badc417b26c6-e7120108063081b7.gif176.011This Loom discusses proposed database schema changes for file references, including how to handle an original flag and foreign keys. The speaker adds an original boolean default true and removes the content type from the added file reference to avoid duplicating file references across versions. Because this prevents a foreign key to a partial index, they recreate a full index on original, with the approach working when original is true or null (nulls are distinct, so it is not an issue). They also note that MyContents needs the original field and mention revisiting whether to avoid multiplying file references and whether content type should be maintained in file reference and included in insertion logic.