We repeatedly ran into the issue that deployment of bounty contracts resulted in the same TX (and eventually contract) being associated with a bounty. This is broken and so this constraint on the Postgres table should help with ensuring that this does not happen anymore.
Before this can be deployed or even tested the respective databases need to be cleared of any records that violate this constraint.
We repeatedly ran into the issue that deployment of bounty contracts resulted in the same TX (and eventually contract) being associated with a bounty. This is broken and so this constraint on the Postgres table should help with ensuring that this does not happen anymore.
Before this can be deployed or even tested the respective databases need to be cleared of any records that violate this constraint.