Problems with Worksets - 06/16/23 02:53 PM
I am having intermittent problems with worksets in version 15.0.3.
I don't use multiple worksets. I have one single workset that I use to automatically restore the windows from the previous PL/SQL Developer session. Today, I closed PL/SQL Developer and then re-opened it about 10 minutes later and the contents of all unsaved SQL windows were lost. The SQL windows were still in the window list but there was an error something like "Unable to read file" for each unsaved SQL window and the contents were lost. This happens at least once every week or so.
Sometimes the entire workset is lost and no windows are opened at all. This happens must less frequently. It has only happened a handful of times since I began using version 15 in April 2022.
I don't usually explicitly save the workset before closing PL/SQL Developer as the documentation states that it is automatically saved when PL/SQL Developer closes.
Is there anything I can do or provide to help debug this issue?
I don't use multiple worksets. I have one single workset that I use to automatically restore the windows from the previous PL/SQL Developer session. Today, I closed PL/SQL Developer and then re-opened it about 10 minutes later and the contents of all unsaved SQL windows were lost. The SQL windows were still in the window list but there was an error something like "Unable to read file" for each unsaved SQL window and the contents were lost. This happens at least once every week or so.
Sometimes the entire workset is lost and no windows are opened at all. This happens must less frequently. It has only happened a handful of times since I began using version 15 in April 2022.
I don't usually explicitly save the workset before closing PL/SQL Developer as the documentation states that it is automatically saved when PL/SQL Developer closes.
Is there anything I can do or provide to help debug this issue?