We have this feature in old school SQL Developer where you can have ‘important’ connections outlined with a color scheme…the connection name is also given this color.
As we’re re-creating our SQL Developer world inside of VS Code, we know what works, we know what people like, we know what people NEED. But, does it makes sense to do a 1:1 lift-and-shift for every feature?
This is one of those features that WILL get done, but the implementation may be different.
For example, did you know you can ALREADY have fun with your connection names?
This probably isn’t enough to give folks what they either want or need, but it is SOMETHING you can do to make things easier to find, navigate. My brain sees those emojis much faster than it can parse the connection names.
You’ll see these in SQLcl as well, for example –
Someone saw my connection names in a tweet or something, and asked, hey, how do you do that?
Literally, just type in the connection name. I grab the emoji off the the innerwebs, and paste it into the editor.
6 Comments
In VS code I have this: π hr@test
In sqlcl “cm list” output is:
ΒΔΓΆΔΊ hr@test
SQL> conn -name ΒΔΓΆΔΊ hr@test
Unknown connection β¬ΕβΕΉβΓββ
SQL>
You prob should change your windows code page to unicode and then when you make your connection, double quote the connection name. I can paste emoji’s (unicode characters) just fine in my Windows 11 terminals.
So what you have should look like this
SQL> conn -name “π hr@test”
Now, it is working. π
Thanks a lot.
Best regards
Awesome, thank you for bringing this up as I’m sure others will run into that.
Nice feature, but with emoji in the connection name sqlcl is unable to connect using conn -name.
It most definitely should be working, can you tell me more?