Hi all.
I'm referring to this discussion (now archived).
SQLDeveloper now correctly compiles the files I open against the current active connection (thank you very much for that).
Unfortunately, a new bug has been introduced:
- open SQLDev
- open conn1
- open fileA
- compile fileA
- close SQLDev
- open SQLDev
- open conn2
- open fileA
At this point SQLDev connects to conn1 (I suppose it somehow remembers the last conn I compiled fileA against).
I really hope I'm missing something obvious, otherwise we're back to square 1, as far as I'm concerned (that is, a behaviour so annoying to render the product practically unusable).
OS X 10.9
SQLDev 4.0.0.13.80
Java 1.7.0_21
Alessandro