build: 8.0.0.1480: large rollback => sandclock only show

[Bernhard S]

Hello,
when you rollback a large transaction the whole PL/SQL Developer main window turns into a sandclock only show. This should not be the case! It should be possible to have the same functionality as you have while the transaction rolled forward. There you still could use other pl/sql developer windows in the the same main window, execute selects, ... As long as you're not creating a new transaction that has to wait on the current one, you should be fine.

 

[Marco Kalter]

How exactly do you perform the rollback? In the SQL Window? In the Command Window? ...?

 

[Bernhard S]

I verified that in SQL Window and Command Window. However in the latest version 8.0.1.1498 the annoying behaviour was gone. So just make sure it won't sneak in again in any future release.

 

[Bernhard S]

This behaviour has sneaked into 8.0.1.1510 again.
I have just updated 1 Mio rows via command window and rolled back via rollback button.
=> Got sandclock and could not use this PSD window for as long as rollback lasted.
I'd suggest you write some unit tests and do regression testing before rolling out new PSD versions to make sure errors like this won't sneak in again.

 

[Marco Kalter]

Nothing has changed in PL/SQL Developer between 8.0.0 and 8.0.3 for commit and rollback processing.

 

[Bernhard S]

I have created a testcase:

create table my_dba_obj as select * from dba_objects;

--repeat following insert a few times:
insert into my_dba_obj select * from my_dba_obj;
commit;

select count(*) from my_dba_obj;

update my_dba_obj o set o.object_id = o.object_id+1;

I repeated the insert several times until I had about 500k rows. The update then took about 20 sec. While the update runs I can use other PSD window items and execute SQLs there in the same PSD. When I issue the rollback via "rollback" command that behaviour is the same. However when I use the "rollback" button instead, I cannot switch to other PSD window items of the same session. The behaviour is basically the same in SQL window and in Command window, just in the latter I eventually get the sandclock when clicking several other window items, while in the first the cursor keeps falsely indicating to be ready to select other windows items, but never lets you activate them.

 

[Marco Kalter]

It is indeed true that the commit and rollback buttons block the main thread of the application. I have added a request to the list of enhancement requests to perform these functions in the background thread of the target window.