2009/8/3 Pavel Stehule <pavel.stehule@gmail.com>:
> 2009/8/2 Euler Taveira de Oliveira <euler@timbira.com>:
>> Tom Lane escreveu:
>>> The real bottom line for to_char issues is almost always that we should
>>> do what Oracle does. Has anyone checked this behavior on Oracle?
>>>
>> That was my point too. See [1].
>>
>> [1] http://archives.postgresql.org/pgsql-hackers/2009-07/msg01870.php
>>
>
> so, Brendan, please, can you adjust patch to raise exception like Oracle?
>
Well, the examples Euler posted in the linked message above were using
E+308. If I'm reading the Oracle docs correctly, that would have
triggered Oracle's data type overflow error before even getting to
to_char(); Oracle's NUMBER type only supports up to E+126. So we
still don't really know how Oracle handles a (legal) value with too
many exponent digits for EEEE.
Euler, could you post results for a number which fits within Oracle's
data type but has three exponent digits (like 1E+100)?
Cheers,
BJ
