feat: add SQLite persistent history with full-text search (closes #125)#200
Open
RavindiFernando wants to merge 1 commit into
Open
feat: add SQLite persistent history with full-text search (closes #125)#200RavindiFernando wants to merge 1 commit into
RavindiFernando wants to merge 1 commit into
Conversation
Owner
|
@RavindiFernando resolve the conflicts |
3e7faf9 to
ba336f6
Compare
ba336f6 to
acab9e6
Compare
Contributor
Author
|
@imDarshanGK , |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Add SQLite-based persistent history with full-text search. Analysis results are now saved server-side in a SQLite database via
aiosqlite. The history panel saves to the backend API after each analysis and falls back to localStorage when the backend is unavailable.Related Issue
Fixes #125
Type of change
Checklist
mainpytest -vand all tests passfeat/fix/docs/test: short descriptionScreenshots (if frontend change)
N/A - backend-only change with frontend JS update (no visible UI change)
Test evidence
pytest -v output :

API demo:
