Actually I do not believe the drop-down on the top right corner ever worked for files, just the worksheet.Hi Gary and apologies for the late reply.
xxsawer wrote:I disagree. To me default should be the connection(s) currently open.
Well basicaly I think that any default sticking of a file to a connection is wrong.
If you really want to have such feature then it has to be configurable and disabled by default.That sounds more reasonable.
I think that first time you open a file you always have to chose a connection.I strongly disagree.
Consider you would have 10 connections opened and opening a file for the first time. To which connection would you attach the file?ideally SQLDev should ask me to which of the currently open connections I want to pin the file. If that's too much work, I can live with not pinning to any (IOW, as it is now). BUT if only ONE connection is open I want SQLDev to pin any file to that connection, without asking anything (IOW, as it worked before).
To remember to which connection was a file attached, you need to remember the full path to the file and the connection. If you have hunderts or even thousands of files then such log would be pretty big. What if I remove some files from my project? There is no way how you can detect this, so the log will contain dead mappings.I don't want SQLDev to remember anything: I work with CVS/SVN and the same file can be compiled on different connections (DEV, TEST, PROD, etc.). Not sure what are you talking about here...
Basicaly I don't understand why need this functionality? You need to attach a file to a connection only when you need to compile it. When I am programing something I usually have only few souces open (e.g. three packages). I doubt anybody opens and changes large number of packages. Are you doing some changes to entire system every day?I don't understand how the number of files should make any difference. You open three packages, fine: don't you need to compile the changes you make? I just don't want to be forced to choose the connection if that can be automated (and, BTW, how many connections do you have? I have hundreds: do you think it's fun scrolling through a list that long?).
We associate files with connections for debugging purposes already.Could you please explain in more detail what does it mean? If it implies that each file has to be tied to a specific connection, I don't think it will address my issue (and could potentially make it worse).