You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Further investigation revealed that the data returned from moralis included a few entries with the same transaction_hash and log_index (triggering the unique constraint) , but a different token_id.
Describe the bug
When running
update_nft
, if the NFT transaction history returns batch transactions, aunique constraint
database error is returned.Further investigation revealed that the data returned from moralis included a few entries with the same
transaction_hash
andlog_index
(triggering the unique constraint) , but a differenttoken_id
.Solution should be to simply include the
token_id
column in the unique constraint group.The text was updated successfully, but these errors were encountered: