Severe bug in command window

I am saying sever as there's no other indication that something is wrong, then common sense.

Code:
SQL> select sum(bytes) from user_segments where segment_type = 'TABLE';

SUM(BYTES)
----------
7166514790

Executed in 0.703 seconds

SQL> select sum(bytes) as a________________________ from user_segments where segment_type = 'TABLE';

A________________________
-------------------------
              71665147904
I knew it could not be only 7 Gb's because I know my database, remembering by date experience, i tried with "a____" ... and I was right.

This is very severe, as could mislead some people into doing something terribly wrong.
 
We'll fix this and switch to exponential notation when the value is longer than the numwidth setting (you can use SET NUMWIDTH to override the default setting of 10).
 
You can edit the login.sql file in the PL/SQL Developer directory and insert the SET NUMWIDTH command there. This will be executed for every Command Window.

The SQL Window does not suffer from this problem.
 
You can enable the SQL Window preference "Number fields to_char" (Tools > Preferences > SQL Window tab page).
 
Yes, but then when I use PL/SQL ordering, the numbers are ordered as strings, thus incorrectly. I know I can use oracle to order them correctly.

I know I can't have everything, but it would be nice if it was optional in v.6 (when to switch to scientific, if at all)
 
What do i have to do, to get no scientific notation in the command window when i do a select * from
?

thx,
 
The only way around this is to use a to_char expression for these columns, so it will not work with a "select * from" statement.
 
Back
Top