user1369: If I've understood the dbsync schema properly then the tx_in table is completely unnecessary. The two fields (tx_in_id & redeemer_id) should just be brought into the tx_out table and left null when a UTXO has not yet been consumed. This would be far more intuitive, or am I missing something?

user382: db-sync is insert only. You need to be able to see what the state was at any particular point in time. If it modified rows that wouldn't allow you to do so.

1369: <p>If I've understood the dbsync schema properly then the <code>tx_in</code> table is completely unnecessary. The two fields (<code>tx_in_id</code> &amp; <code>redeemer_id</code>) should just be brought into the <code>tx_out</code> table and left null when a UTXO has not yet been consumed. This would be far more intuitive, or am I missing something?</p>
 382: <p>db-sync is insert only. You need to be able to see what the state was at any particular point in time. If it modified rows that wouldn't allow you to do so.</p>
