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 SQL update instead of Delete/Read mechanism for Database update #424

Open
paetz opened this issue May 2, 2023 · 0 comments
Open

Use SQL update instead of Delete/Read mechanism for Database update #424

paetz opened this issue May 2, 2023 · 0 comments
Labels
feature New feature or request
Projects
Milestone

Comments

@paetz
Copy link
Collaborator

paetz commented May 2, 2023

When updating the DB, the current approach is to delete and re-add all objects.
This results in a huge database writing effort and hence, consumes a lot of runtime.

Better use the SQL update mechanism for existing object IDs and only delete outdated objects or add new objects, respectively.

@paetz paetz added the feature New feature or request label May 2, 2023
@paetz paetz added this to the v0.8.0 milestone May 2, 2023
@paetz paetz added this to To do in YacGuide via automation May 2, 2023
@chrgernoe chrgernoe changed the title Use SQL update instead of Delete/Readd mechanism for Database update Use SQL update instead of Delete/Read mechanism for Database update May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
YacGuide
  
To do
Development

No branches or pull requests

1 participant