From: | Pavel Raiskup <praiskup(at)redhat(dot)com> |
---|---|
To: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
Cc: | pgsql-odbc(at)postgresql(dot)org, Hiroshi Saito <hiroshi(at)winpg(dot)jp> |
Subject: | Re: psqlODBC 09.05.0200 Released |
Date: | 2016-04-19 05:20:29 |
Message-ID: | 1515578.djyByuRrr5@nb.usersys.redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-odbc |
[dropping the announce list, sorry for not doing it before]
On Tuesday 19 of April 2016 07:50:30 Inoue, Hiroshi wrote:
> The commit handles the bug report
> [ODBC] Issue with Money field using ODBC to Access database
> posted by John Van De Giessen on Febrary 14.
Thanks for the reference. I have to look at the thread once more, as I
don't fully understand how that patch is relevant to MONEY type.
> The bug was introduced in 9.5.0100 and the regression test result maybe
> modified.
The test case shows that psqlodbc uses 'numeric' type for
SQL_FLOAT/SQL_DOUBLE id (instead of 'double precision' used before, or
'float8'). This sounds like a bug, or is this really expected? If yes, I
can submit a patch fixing the test-case -- but it does not feel right.
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Benoît Carpentier | 2016-04-20 13:22:43 | Benetl, a free ETL tool for postgreSQL, out in version 4.7 |
Previous Message | Kouhei Sutou | 2016-04-19 04:07:37 | [ANN] PGroonga 1.0.6 - Make PostgreSQL fast full text search platform for all languages |
From | Date | Subject | |
---|---|---|---|
Next Message | Venkatesan, Sekhar | 2016-04-19 06:53:51 | PostgreSQL: SQLSetPos fails with SetPos update return error. |
Previous Message | Inoue, Hiroshi | 2016-04-18 22:50:30 | Re: psqlODBC 09.05.0200 Released |