Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messages have moved to a new tab #18515

Open
ERPrun-DM opened this issue Dec 17, 2024 · 3 comments
Open

Messages have moved to a new tab #18515

ERPrun-DM opened this issue Dec 17, 2024 · 3 comments
Milestone

Comments

@ERPrun-DM
Copy link

ERPrun-DM commented Dec 17, 2024

When writing T-SQL you quite often have to compare one result set with another one by firing off 2 SELECT-statements or more within 1 excution tab.
Since the latest version has the 'improvement' that messages to those results have got moved to a seperate tab you cannot compare amount of rows or any hickups between statements without clicking back and forth. This is not how it used to be and it is very inconvenient. Even SSMS's design is like how it used to be.

@Benjin Benjin added Area - Query Result User-filed Filed by a public user labels Dec 17, 2024
@Benjin Benjin assigned jdesai-24 and unassigned jdesai-24 Dec 17, 2024
@Benjin
Copy link
Contributor

Benjin commented Dec 17, 2024

@ERPrun-DM Thank you for your feedback! We modeled this design after how Azure Data Studio and SSMS display their results, so VS Code's old design was the odd one out in this case.

New VS Code:
Image

Old VS Code:
Image

SSMS:
Image

Azure Data Studio:
Image

@ERPrun-DM
Copy link
Author

ERPrun-DM commented Dec 18, 2024

I get it and I haven been working on an old SSMS version, not knowing it could change. However, I wish there was an option within the settings you could choose from where to prompt messages.

@Benjin
Copy link
Contributor

Benjin commented Dec 18, 2024

Noted! I'll keep this issue open as a feature request. @croblesm @jdesai-24 do you have any thoughts on this idea?

@Benjin Benjin added this to the Backlog milestone Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants