After unchecking this option, Toad displays the value like this:īetter.

During the above tests, this option was checked. In the Toad options (version 12), there’s an option called “Display large numbers in Scientific Notation”. So the whole number is stored in the database, apparently Toad rounds this value. Display problems, let’s try with a TO_CHAR using a somewhat larger format mask: SQL> SELECT TO_CHAR(BIGNUM,'99999999999.99999999') SQL> SELECT * 2 FROM NUMTEST BIGNUM - 1234567890 SQL> CREATE TABLE NUMTEST (BIGNUM NUMBER(16,6)) Table created. So what’s the problem with the 16,6 length? Let’s revert to our first testcase and this time don’t check in Toad (our IDE), but in trusty old SQL*Plus: SQL> DROP TABLE NUMTEST Table dropped. DROP TABLE NUMTEST CREATE TABLE NUMTEST(BIGNUM NUMBER(10,6)) INSERT INTO NUMTEST VALUES(1234.123456) COMMIT SELECT * FROM NUMTEST Hm? Only 5 decimals, and the value is rounded? How can this be? Let’s try another testcase. CREATE TABLE NUMTEST(BIGNUM NUMBER(16,6)) INSERT INTO NUMTEST VALUES (1234567890.123456) COMMIT SELECT * FROM NUMTEST So, if we insert a value of 1234567890.123456, we expect this to succeed. It also means the value can not grow beyond 10 digits. As we all know, this defines a numeric column as having 16 digits in total, of which 6 decimals. An application I was working on had several tables with columns defined as a NUMBER(16,6).

Toad pl sql