Re: WIP: to_char, support for EEEE format

From: Brendan Jurd <direvus(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: to_char, support for EEEE format
Date: 2009-08-02 22:27:01
Message-ID: 37ed240d0908021527r38b699f3t1a05a8570b23437@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2009/8/3 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> 2009/8/2 Euler Taveira de Oliveira <euler(at)timbira(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-02 22:35:45 Re: machine-readable explain output v4
Previous Message Tom Lane 2009-08-02 22:17:38 Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT