Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use blockHash/logIndex as the unique placement ID #8

Merged
merged 2 commits into from
Sep 28, 2022

Conversation

will-wow
Copy link
Contributor

Goal

Use the blockHash/logIndex to uniquely identify placement events

Solution

  • make blockHash/logIndex the composite primary key for placements
  • use ${blockHash}_${logIndex} as the ID in geoJson files
  • do an upsert to do idempotent handling of placements in /sync

Notes

  • This will make you blow your db away 😞 , because we need to re-add block hashes and log ids. But you can re-sync to get all the existing stuff back

Base automatically changed from feature/docs-and-linting to develop September 28, 2022 04:38
@will-wow will-wow merged commit fd3fcea into develop Sep 28, 2022
@will-wow will-wow deleted the feature/unique-placements branch September 28, 2022 04:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant