Revision cfb2417fecfff890ec19fb60405df0c709b89fa6 authored by Valentin Lorentz on 26 March 2021, 15:03:27 UTC, committed by Valentin Lorentz on 26 March 2021, 15:08:13 UTC
It did not make sense for multiple reasons: 1. two extids can point to the same target (eg. extids with type git and git-sha256; or two package managers with different checksums) 2. inserting two objects with the same target or extid in a single call actually wrote both, but would crash when reading 3. inserting extid1 then extid2 would write both to Kafka, but only extid1 would be inserted. When replaying on a new DB, extid2 may be inserted and extid1 ignored Points 2 and 3 are simply fixable bugs, but 1 is an issue by design, and this commit fixes all of them at once.
1 parent ac6f642
| File | Mode | Size |
|---|---|---|
| bin | ||
| doc | ||
| json | ||
| upgrades | ||
| .gitignore | -rw-r--r-- | 26 bytes |
| Makefile | -rw-r--r-- | 1.5 KB |
| TODO | -rw-r--r-- | 1.1 KB |
| clusters.dot | -rw-r--r-- | 2.0 KB |
Computing file changes ...
