Skip to content

Conversation

@tmm1
Copy link
Contributor

@tmm1 tmm1 commented Aug 17, 2025

fixes #260807

cc @bpasero

Copy link
Member

@bpasero bpasero left a comment

Choose a reason for hiding this comment

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

Actually, lets keep the CREATE statement as it was, my perf testing does not show any improvements changing that and I feel we should not have a mix of old and new schema here. Besides, the CREATE statement as it was seems better to explain the intent.

I also played around with setting the key to PRIMARY KEY but that does not seem to yield significant improvements.

Thanks for reporting and fixing this. This kind of contribution requires some good understanding of our code 👏

@bpasero bpasero added this to the August 2025 milestone Aug 18, 2025
@bpasero bpasero merged commit 490afdd into microsoft:main Aug 18, 2025
17 checks passed
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Oct 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Slow ItemTable SQL queries

3 participants