Skip to content

fix: re-pull from source#101

Merged
Xetera merged 6 commits intomainfrom
feat-repull-from-source
Mar 30, 2026
Merged

fix: re-pull from source#101
Xetera merged 6 commits intomainfrom
feat-repull-from-source

Conversation

@Xetera
Copy link
Copy Markdown
Collaborator

@Xetera Xetera commented Mar 27, 2026

This change should allow pulling from source without restarting analyzer

Xetera added 4 commits March 27, 2026 16:04
this pr adds the concept of database generations without restarting
analyzer. That should allow us to continue refreshing from source db
conveniently with an HTTP request
@Xetera Xetera force-pushed the feat-repull-from-source branch from e6e3435 to 8de20f1 Compare March 27, 2026 13:05
Copy link
Copy Markdown

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Query Doctor Analysis

View full run details

27 queries analyzed

2 pre-existing issues

Using assumed statistics (10000 rows/table). For better results, sync production stats.

@Xetera
Copy link
Copy Markdown
Collaborator Author

Xetera commented Mar 27, 2026

Looking into the failing tests. This needs some changes to how existing query optimizations work with new database generations.

@Xetera Xetera merged commit 83d96a3 into main Mar 30, 2026
6 checks passed
@Xetera Xetera deleted the feat-repull-from-source branch March 30, 2026 16:41
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.

2 participants