Skip to content

fix use info schema panic#8931

Merged
max-hoffman merged 2 commits intomainfrom
max/use-info-schema-panic
Mar 5, 2025
Merged

fix use info schema panic#8931
max-hoffman merged 2 commits intomainfrom
max/use-info-schema-panic

Conversation

@max-hoffman
Copy link
Copy Markdown
Contributor

@max-hoffman max-hoffman commented Mar 4, 2025

The active database being information_schema causes some issues with branch state/working sets.
gms side: dolthub/go-mysql-server#2873
fixes: #8930 (comment)

@coffeegoddd
Copy link
Copy Markdown
Contributor

@max-hoffman DOLT

comparing_percentages
100.000000 to 100.000000
version result total
78612a9 ok 5937457
version total_tests
78612a9 5937457
correctness_percentage
100.0

Copy link
Copy Markdown
Contributor

@jycor jycor left a comment

Choose a reason for hiding this comment

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

LGTM, but maybe add a test with information_schema?

@coffeegoddd
Copy link
Copy Markdown
Contributor

@max-hoffman DOLT

comparing_percentages
100.000000 to 100.000000
version result total
305da29 ok 5937457
version total_tests
305da29 5937457
correctness_percentage
100.0

@max-hoffman max-hoffman merged commit 0565b03 into main Mar 5, 2025
20 of 21 checks passed
@max-hoffman max-hoffman deleted the max/use-info-schema-panic branch March 5, 2025 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Panic when browsing database tables after connecting to INFORMATION_SCHEMA via SQLTools extension

3 participants