add support for incremental updates #34
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Incremental Backup Feature - Pull Request Summary
Overview
Added --checkpoint-file functionality to enable incremental backups, significantly reducing backup time for users who run the script regularly. This is an optional flag
Problem Solved
Previously, every run was a full backup, requiring downloading all submissions regardless of whether they had been processed before. This made regular backups slower than necessary.
Solution
The checkpoint feature stores the Unix timestamp of the newest processed submission. Subsequent runs only process submissions newer than the checkpoint, leveraging LeetCode's reverse chronological API ordering to stop early when reaching older submissions.
Key Features
Usage
Implementation Details
This feature makes regular LeetCode backups practical for active users while maintaining the robustness of the existing codebase.