| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Johan Miller" <johanmiller(at)gmail(dot)com> |
| Cc: | "Kris Jurka" <jurka(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Problem with java infinity mapping to postgres real column type |
| Date: | 2008-07-19 00:51:14 |
| Message-ID: | 11957.1216428674@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
"Johan Miller" <johanmiller(at)gmail(dot)com> writes:
> On Thu, Jul 17, 2008 at 08:22, Kris Jurka <jurka(at)ejurka(dot)com> wrote:
>> I see this in the 8.3 release notes:
>>
>> Fix float4/float8 to handle Infinity and NAN (Not A Number) consistently
>> (Bruce) The code formerly was not consistent about distinguishing Infinity
>> from overflow conditions.
> What would be the options to handle this on earlier version where it is not
> fixed? Would it be a possibility that this will get changed in the 8.1 and
> 8.2 versions also?
I believe the conclusion was that that change shouldn't be back-patched
because it would be a behavioral change that might break applications.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter | 2008-07-20 10:32:51 | numeric type |
| Previous Message | Johan Miller | 2008-07-17 11:16:30 | Re: Problem with java infinity mapping to postgres real column type |