if a file is associated with only one database object (like ERR_DEMO in the above example), then we know what is the "default" connection, so that a user can be spared from one extra step of setting the connection whenever opening err_demo.pkb.So if I open err_demo.pkb and I have ONE connection open which is different from what you consider "default", clicking Compile will open the default connection and compile against it?
Vadim Tropashko wrote:Thank you for pursuing this Vadim.
I failed to reproduce the problem. Step-by-step test case:
1. Create file scott.mysimplepkg.pks
create or replace PACKAGE scott.mySimplePKG AS
FUNCTION add (par1 number, par2 number)
2. Open file. It is opened in PL/SQL editor (not worksheet). The connection combobox is empty.
3. Select connection. It is immediate if connection is active, and some time to connect, otherwise. (The connection widget is not associated with the editor content by any means).
Can you please elaborate?
Lets summarize what we have:
1. Before 3.2 newly opened file based PL/SQL editor were associated with "default" connection, and as xxsawer noted this was a bug.
2. After 3.2 newly opened editor is not associated with any connection and requires user to explicitly choose one.
After little reflection it seems that correct fix is for a newly opened editor to look into project.qbql mapping, and if there is an entry there, then choose this connection (which, of course, can be changed if user wants so). Am I missing any other usage scenario?
Edit: implemented for EA2.