-
Notifications
You must be signed in to change notification settings - Fork 3
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
Improve re-running the merger #27
Comments
Current workaround (includes adding is_merged flag to address and charging table).
|
For now implemented a new option (delete_data), which performs the actions above, will create a PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when re-running the merger one has to basically throw away the db and has to recreate it. A more convenient way is to persist merged stations isolated from the imported data and only delete the according table.
Further ideas:
MergedStationSource
can be stored in the newmerged_stations
table andMergedStationSource
entity and table can be removedThe text was updated successfully, but these errors were encountered: