search

hoophq / sequence

Immutable, scalable, and easy to use ledger service.
Apache License 2.0
493 stars 31 forks source link

Duplicate entry prevention #18

Closed minvs1 closed 3 years ago

minvs1 commented 4 years ago

In some cases backend could generate multiple requests to the ledger with the same transaction data resulting in a duplicate entry. One way to prevent this could be setting transaction id to HASH(order.id) - posting this more than once should result in failure.

Is this possible? Or there is a better approach to this?

andriosrobert commented 3 years ago

Hey @minvs1, we will solve this with #8

Closing this one for now.