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

FeatureSuggestion : Object Browser / Object Lookup #962

Closed
valkcon opened this issue Jul 28, 2017 · 3 comments
Closed

FeatureSuggestion : Object Browser / Object Lookup #962

valkcon opened this issue Jul 28, 2017 · 3 comments

Comments

@valkcon
Copy link

valkcon commented Jul 28, 2017

Looks great so far, I'm almost (but not quite) convinced to use this daily....however:

A db-object-browser would be great. Given intellisense is already a feature, shouldn't this be almost as simple as a Pretty-Dump-to-someTreeViewThingy of the intellisense data?

We tend to use StoredProcedures a lot, it's difficult to actually load a definition of a StoredProc in the extension (or view, or table) without first writing some sql and then using "go to definition". If I want to alter procedure dbo.deleteWholeDataBase, I have to type exec dbo.deleteWholeDataBase and then use "go to definition", there's an inherent danger there I might actually execute exec dbo.deleteWholeDataBase!!

Actually, a full-ux-object-browser is not entirely required, just a single auto-complete-lookup input for the intellisense-data with a button beside results for "go to definition" would be great. Maybe even possible to put this into the command pallette. In fact a simpler lookup for db-object-name-contains could even be more useful than a treeview as half the time I forget which schema has the StProc or view I'm looking for, or that one schema StProc is calling the other.

Just a few thoughts.

@sean256
Copy link

sean256 commented Oct 12, 2017

I came here to ask for the same thing. A UI view would be ideal!

@mika76
Copy link

mika76 commented Jan 8, 2018

I think this is the same request as #1031 ? (or vica versa)

@abist
Copy link
Contributor

abist commented Sep 16, 2019

Closing this issue as it's being tracked here - #586

@abist abist closed this as completed Sep 16, 2019
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

5 participants