Packages content is not updated when switching connection

In Version 7.1.5.1398 against a 10g db with a 10g client

the package body View or Edit functions from the Browser can lead to confusion in view mode and even worse in edit mode as the Program window contents are not refreshed but the windows list is updated to the new connection when switching from a base to another

 

[Marco Kalter]

I tried this, but both the window list and the window title itself keep the original database indication. Can you let me know the exact steps to reproduce this?

 

Hi Marco,

thanks for your interest,

Here are the steps:
0. in our example we have several databases with the same schemas containing different versions of packages

1. open a session on db01
-> we are connected, ok

2. edit a package_body1 from user1 with the browser
-> the package body is displayed in a new program window with source from db01, ok
-> the main window title says "view source of package body1 user1.package1@db01", ok
-> the window list displays "view source of package body1 user1.package1@db01", ok

3. close the session from db01
-> we are disconnected, ok

4. open a session on db02
-> we are connected to db02

5. edit a package_body1 from user1 with the browser
-> the package body is displayed in the same program window with source from db01, NOT ok
-> the main window title says "view source of package body user1.package1@db02", ok
-> the window list displays "view source of package body user1.package1@db02", ok
->
-> the window titles are correct but the package source code is not refreshed, NOT ok

-> the same scenarion can be applyed in Edit mode and this can lead to regressions

thanks
Seb

 

[Marco van der Linden]

I agree with Seb. This is true even if you don't change connections.

Step 1: Open a package in the editor
Step 2: Make some changes
Step 3: In the browser select same package for editing

I would expect the package to 'reload' in the already open editor, but this does not happen.

It seems PLD recognizes that an editor is already open for said object, but does not refresh window contents.

 

[Marco Kalter]

It seems PLD recognizes that an editor is already open for said object, but does not refresh window contents.

That is correct. It will merely bring the editor to the front, if necessary, but will not override you changes. Maybe we should add a "Refresh?" message.

 

[Marco van der Linden]

Maybe we should add a "Refresh?" message

That would be a good options. At least you are aware that the window content is not refreshed/reloaded automatically.

 

I think that something great would be to open another edit or view window when the window title changes,
this way in my scenario above for example we would have both packages sources in different edit windows, like:

"Edit source of package body1 user1.package1@db01"
and the other with
"Edit source of package body1 user1.package1@db02"

the same for the "View source ..."

Seb

 

[mike]

A refresh message would be OK.

I like that it doesn't change what's in the editor when we change databases. I have needed many times to copy a package from one database to another. I open it up, change instances and compile. That's easy.