Skip to content

⚡ Optimize LibraryRepository.updateNovelInfo with direct SQL update#42

Merged
Aatricks merged 1 commit intomainfrom
perf/optimize-update-novel-info-13548552109577409894
Feb 13, 2026
Merged

⚡ Optimize LibraryRepository.updateNovelInfo with direct SQL update#42
Aatricks merged 1 commit intomainfrom
perf/optimize-update-novel-info-13548552109577409894

Conversation

@Aatricks
Copy link
Owner

💡 What: Replaced the inefficient in-memory update logic in LibraryRepository.updateNovelInfo with a direct SQL UPDATE query via LibraryDao.

🎯 Why: The previous implementation fetched all library items into memory, filtered them by baseTitle, created copies with updated fields, and then inserted them back. This was an O(N) operation with significant memory overhead for large libraries. The new implementation is an O(1) (or O(M) where M is the number of matching chapters) database operation, which is significantly faster and more memory-efficient.

📊 Measured Improvement:

  • Verified via LibraryRepositoryUpdateTest that getAllItems() is no longer called during the update operation.
  • The operation now executes a single SQL statement instead of loading potentially thousands of objects into the heap.

PR created automatically by Jules for task 13548552109577409894 started by @Aatricks

- Replaced in-memory filtering and updating of library items with a targeted SQL UPDATE query in LibraryDao.
- Added `updateNovelInfo` method to `LibraryDao` that updates `baseNovelUrl` and `sourceName` for all items sharing the same `baseTitle`.
- Refactored `LibraryRepository.updateNovelInfo` to use the new DAO method.
- Added `LibraryRepositoryUpdateTest` to verify the new implementation calls the DAO method correctly and does not perform a full table scan.

Co-authored-by: Aatricks <113598245+Aatricks@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@Aatricks Aatricks merged commit fd1a885 into main Feb 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant