Remove handling of duplicate storage diffs in watcher

- Can push this responsibility down to the transformers
- Update docs to reflect that transformers should handle duplicates
This commit is contained in:
Rob Mulholand
2019-05-20 13:29:09 -05:00
parent 79765c7998
commit e2909797fc
6 changed files with 5 additions and 30 deletions
@@ -100,6 +100,7 @@ type Repository interface {
A contract-specific implementation of the repository interface enables the transformer to write the decoded storage value to the appropriate table in postgres.
The `Create` function is expected to recognize and persist a given storage value by the variable's name, as indicated on the row's metadata.
Note: we advise silently discarding duplicates in `Create` - as it's possible that you may read the same diff several times, and an error will trigger the storage watcher to queue that diff for later processing.
The `SetDB` function is required for the repository to connect to the database.