Oracle FLOAT(126) can't handle +/-1.79E+308 to but MS/MySQL/Postgres can
786949Jul 22 2010 — edited Jul 22 2010SQL Server, MySQL and Postgres can all have DOUBLE that is a 64bit floating point number holding the range -1.79E+308 to 1.79E+308. The Oracle docs say to use FLOAT(126) as DOUBLE, but it cannot handle this range, it only seems to cope somewhere around 1E+125
I've tested on both Oracle 10g and Oracle 10g Express.
How can I get the proper range for 64bit floating point numbers? What is the absolute maximum range an Oracle floating point number can handle? I've had the exact same issues with BINARY_DOUBLE not taking more than 1E+125
Lyle