schema won't disappear from the list when dropped

[DevDorrejo]

I am working with a dB, and must re-do the schema every time, but the extension won't correctly reflect the actual state of the dB, I tried to reconnect, refresh, but the nonexistent schema still appears.

[mmcfarland]

Thanks @DevDorrejo, sorry you're hitting this behavior. This may be due to our node "refresh command" working only for direct children. After dropping (or creating a new schema), can you right-click on the Schemas node (not the <database name> node) and selecting the "Refresh" option?

We are tracking an issue to cascade the refresh down the tree, but I'm curious if there is another issue that you're hitting where the schema's are being cached longer than they should be. I appreciate your help in debugging this.

[mmcfarland]

Similar to #199

[mmcfarland]

Hi @DevDorrejo, we've improved how Object Explorer handles refresh in v1.19.0 (pre-release). Dropped schemas and other deleted objects should now disappear after a refresh on any server tree node without needing to reconnect. Could you give it a try and let us know if it resolves the issue?