Yes, pl/sql file is associated with the last connection it has been compiled against. If you want to change this association, then just switch the connection in the dropbox and recompile. The reason why opened connection in the navigator is ignored is because a typical user has more than one connection opened, thus rendering the idea of "default" connection flawed.
Yes, pl/sql file is associated with the last connection it has been compiled against. If you want to change this association, then just switch the connection in the dropbox and recompile.
Let's see if I understand correctly.
Before, if I wanted to compile the same file against different connections, I was forced to choose one (even though only ONE was opened).
After the "fix", not only I have to take the same action, but I also have to close a connection that's opened against my wish.
Sorry, that's hardly an improvement in my eyes...
So I have to ask again: can you remove (or make optional) that nasty association?
In case someone else is facing the same problem, I ended up writing a simple script that, before launching SQLDeveloper, removes
The other way around it is to compile the file against two different databases. If file is associated against more than one connection (i.e. there are two records in project.qbql), then the default connection in drop box would be selected from active open connections (but only if there is single one).
Jeff suggested that if
Tools > Prefs > Code Editor > Link Stored Procedures to Files
is unchecked, then the default connection shouldn't be chosen from project.qbql, and I agree to fix that.