Re: NUMERIC type makes trouble in MS Access

From: Jan Wieck <jan(at)wi3ck(dot)info>
To: Tobias Wendorff <tobias(dot)wendorff(at)tu-dortmund(dot)de>
Cc: "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>, pgsql-odbc(at)lists(dot)postgresql(dot)org
Subject: Re: NUMERIC type makes trouble in MS Access
Date: 2018-05-27 03:18:12
Message-ID: CAGBW59dLVsj+wO9AGqtQ7EUSnNO-tXuAhh==G+muhLLPwO34Gg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Anything that is exact precision in the database should never be handled as
"double" in any driver. That is a serious bug and a possible violation of
accounting laws in many countries.

That is assuming "double" in this case means "double precision floating
point" as in C's double type.

Best Regards,
Jan

On Sat, May 26, 2018 at 10:58 PM, Tobias Wendorff <
tobias(dot)wendorff(at)tu-dortmund(dot)de> wrote:

> Some additional information about supported functions and mappings:
>
> https://www.devart.com/odbc/postgresql/docs/supported_data_types.htm
> https://www.devart.com/odbc/postgresql/docs/supported_
> odbc_api_functions.htm
>
> Does PGSQL-ODBC map NUMERIC the same way (to SQL_NUMERIC)?
>
>
>

--
Jan Wieck
Senior Postgres Architect
http://pgblog.wi3ck.info

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Tobias Wendorff 2018-05-27 16:35:59 Re: NUMERIC type makes trouble in MS Access
Previous Message Tobias Wendorff 2018-05-27 02:58:10 Re: NUMERIC type makes trouble in MS Access