Claus Pedersen
Member³
I have a command window script which causes Oracle errors (unique constraint).
When the errors are marked with the red error 'wave' lines (fills the entire screen), the performance (the number of lines executed pr. minute) is severely reduced (a magnitude).
Steps to reproduce:
On the scott/tiger schema, in a command window, I copy-paste a lot of the same lines:
insert into emp values(7369, 'SMITH', 'CLERK', 7902, SYSDATE, 800, null, 20);
(e.g. 500 identical lines)
These inserts will generate an Oracle error: ORA-00001: unique constraint violated.
On my system, approx. 300 lines are executed per minute. This is OK.
But now I click on one of the Oracle error messages on the screen. All lines are now suddenly marked with red 'wave' underlines, and the performance is reduced to approx. 30 lines per minute, i.e. a reduction with a factor 10.
When creating a lot of objects/inserting many rows via a script, this is unbearable. The red underlines are persistent, even if you run the script again. The only way to 'reset' this behaviour, is to close the command window and open a new.
Please fix this behaviour.
When the errors are marked with the red error 'wave' lines (fills the entire screen), the performance (the number of lines executed pr. minute) is severely reduced (a magnitude).
Steps to reproduce:
On the scott/tiger schema, in a command window, I copy-paste a lot of the same lines:
insert into emp values(7369, 'SMITH', 'CLERK', 7902, SYSDATE, 800, null, 20);
(e.g. 500 identical lines)
These inserts will generate an Oracle error: ORA-00001: unique constraint violated.
On my system, approx. 300 lines are executed per minute. This is OK.
But now I click on one of the Oracle error messages on the screen. All lines are now suddenly marked with red 'wave' underlines, and the performance is reduced to approx. 30 lines per minute, i.e. a reduction with a factor 10.
When creating a lot of objects/inserting many rows via a script, this is unbearable. The red underlines are persistent, even if you run the script again. The only way to 'reset' this behaviour, is to close the command window and open a new.
Please fix this behaviour.
