Wait... it gets worse! I only just realized that the "@" is restricted. I have many different accounts on each database for testing purposes, so this means my standard of:
is now useless... so what, I start replacing a universally accepted naming standard with something random of my own design? Please, PLEASE at least let us use "@" in the Connection Name.
Why - I'm not sure there's anything we can say that will make you happy here, but the change was made to address some low level framework bugs.
You can keep your old connection names. As a workaround, just manually edit the connections XML file with SQL Developer closed.
Thanks for the reply... and the workaround. It's rare that I edit my Service Names (obviously, or I would have hit this ages ago), so I'll just have to edit the XML by hand. Is there at least a bug/feature request somewhere in the system so that this can get worked on in the future? I'm sure I'm not the only person to be missing "@".
1 person found this helpful
You could open an SR for an enhancement request. But believe me, we already know people want this flexibility back and it's on our to-do list.
I also used '@' for my connection names. I've since replaced them with 'at' - seems to work OK.
I've opened an SR to add my voice:
Thanks for your help.