| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Thangavel, Parameswaran" <Parameswaran(dot)Thangavel(at)rsa(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgresSQL 10 | Driver 42.2.5 | Float Conversion Issue |
| Date: | 2020-10-20 16:50:46 |
| Message-ID: | CAKFQuwY3-0uQqhpBPfUz9_SQ7Z5b=LqG1CHy-=b7GHyR1SfLBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 16, 2020 at 6:32 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Friday, October 16, 2020, Thangavel, Parameswaran <
> Parameswaran(dot)Thangavel(at)rsa(dot)com> wrote:
>>
>> Any thoughts on why this behavior, Is this expected?
>>
>
> Not immediately, can you demonstrate the problem without using JDBC? The
> JDBC project has its own issues setup on GitHub.
>
So, confirming the following query result on head.
select '1234567'::float4::numeric; -- 1234570
Not tested on 9.4.1 (or the last current 9.4.26 release.
The open question is whether the change in result is a bug. I'll agree it
is not expected; but then again floating point and numeric compatibility is
not something that I am expecting to make sense at a high-level; the devil
is in the details.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-10-20 16:56:49 | Re: ECPG bug: "unterminated quoted identifier" |
| Previous Message | Peter Eisentraut | 2020-10-20 16:41:38 | Re: invalid alloc size error possible in shm_mq |