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

Incremental import #189

Open
scy opened this issue Oct 17, 2023 · 1 comment
Open

Incremental import #189

scy opened this issue Oct 17, 2023 · 1 comment
Labels
area:backend Related to the server component flag:caveat Might be confusing or cause problems for third-party users prio:B Major impact, but not essential type:enhancement New feature or request

Comments

@scy
Copy link
Collaborator

scy commented Oct 17, 2023

Currently, importing new MEPs into an existing database is not really possibly. Neither is “remove all MEPs from the database that do not appear in this most recent import”. Instead, all imports assume an empty database.

The possibility to do this should be implemented, because throwing away the live data during a running campaign isn’t ideal, to put it mildly.

Care must be taken not to break existing relationships or assumptions.

@scy scy added type:enhancement New feature or request area:backend Related to the server component prio:B Major impact, but not essential labels Oct 17, 2023
@scy scy added this to the 4.0: public release milestone Oct 17, 2023
@jbethune
Copy link
Collaborator

Looks like we would need to check if an entry already exists around here. I think that deleting MEPs/destinations from the database should not be part of the import functionality but a different feature in order to keeps simple and to distinguish constructive and destructive actions.

@scy scy added the flag:caveat Might be confusing or cause problems for third-party users label Dec 15, 2024
@scy scy removed this from the 4.0: public release milestone Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:backend Related to the server component flag:caveat Might be confusing or cause problems for third-party users prio:B Major impact, but not essential type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants