People starting to take a look at and use our new VS Code Extension – THANK YOU! And some of you are starting to ask questions.
Questions like, “Hey, where is the schema browser?”
And I’m saying, “I hear you, but this is effectively version 1.0 of the product – stay tuned!”
But let’s talk about what you can do RIGHT NOW.
Your schema & the Tree
Find your object type, expand, click to open the object.
Your requests also include:
- filters, we need filters because we have lots of tables!
- can we disable opening the object just because we clicked on it?
We hear you, and we’re on it.
Other schemas and the tree
Scroll down to our old friend, “Other Users,” and repeat the steps above.
And yes, we know, some of you have THOUSANDS of schemas, so again, you need filters. I have to admit, I’m not a fan of this ‘tree on a tree’ pattern, but it does work. It’s just too many clicks, which is why we created the schema browser in the old SQLDev.
We interrupt this blog on nav to show you a trick.
In VS Code you can clearly have multiple files open at once, and you can even have multiple files taking focus at once. You can do the same for your database objects, as we treat the contents of your database as a FILE.
A few different ways to achieve this, but you can drag and drop the document tab (where it says ‘EMPLOYEES’ over to the right, till you see it ghost-paint the new docking point.
Opening your objects from your code.
I showed you this in yesterday’s post.
But repetition is good for both of us, let’s show it, again.
Using the OS / File Breadcrumbs
Remember when I said like, 15 seconds ago, “as we treat the contents of your database as a FILE?”
What’s that mean?
These drop lists are keyboard navigable, meaning I can simply key into the type of object, expand it by hitting →, typing again to get to the object name, and then hitting ENTER to open the object.
This is not the end.
We’re only getting started! If you’re running into issues, have problems, or suggestions, we’re taking those on our Community Forum!