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

Optionally process transactions in the background #592

Closed
DavidMStraub opened this issue Dec 28, 2024 · 0 comments · Fixed by #593
Closed

Optionally process transactions in the background #592

DavidMStraub opened this issue Dec 28, 2024 · 0 comments · Fixed by #593
Assignees

Comments

@DavidMStraub
Copy link
Member

The transactions endpoint is used for raw database transactions, which is used in particular by the sync addon (but is also required for the future revert option #511). Right now, this is done synchronously. But it includes updating the full-text and semantic search indexes. For a large number of transactions (e.g. syncing very out-of-sync trees), this can take very long, in particular with semantic search enabled, so we should process it in the background. For backwards compatibility, background processing should be optional.

@DavidMStraub DavidMStraub self-assigned this Dec 28, 2024
@DavidMStraub DavidMStraub moved this to High Priority in Gramps Web Roadmap Dec 28, 2024
@DavidMStraub DavidMStraub moved this from High Priority to In Progress in Gramps Web Roadmap Dec 28, 2024
@DavidMStraub DavidMStraub moved this from In Progress to Recently Completed in Gramps Web Roadmap Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Recently Completed
Development

Successfully merging a pull request may close this issue.

1 participant