Merged
Conversation
Results Exports that included column subsets incorrectly calculated the "end" column. This resulted in these exports having the correct number of rows, but no data, as the column interation was empty.
lossyrob
approved these changes
Mar 19, 2025
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
2 participants
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.
Results Exports that included column subsets (selections from the results viewer) incorrectly calculated the "end" column. This resulted in these exports having the correct number of rows, but no data, as the column range produced an empty iteration.
Also add indentation formatting to "scripts" from the ScriptingService, which were previously without indentation.
Fixes https://github.com/azure-data-database-platform/vs-code-postgresql/issues/157
Fixes https://github.com/azure-data-database-platform/vs-code-postgresql/issues/175