| From: | "Tobias Wendorff" <tobias(dot)wendorff(at)tu-dortmund(dot)de> |
|---|---|
| To: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
| Cc: | "Craig Ringer" <craig(at)2ndquadrant(dot)com>, "Jan Wieck" <jan(at)wi3ck(dot)info>, pgsql-odbc(at)lists(dot)postgresql(dot)org |
| Subject: | Re: NUMERIC type makes trouble in MS Access |
| Date: | 2018-06-01 14:07:51 |
| Message-ID: | 4195078241775e0c8703dd098b65c3fb.squirrel@webmail.tu-dortmund.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi Hiroshi,
Am Di, 29.05.2018, 14:20 schrieb Inoue, Hiroshi:
>
> I added *memo* and removed *numeric* because default means
> *numeric*.
Thanks it works nice. What do you think about extending this feature
to always apply it to NUMERIC - even when it has a scale and precision?
When having a column with NUMERIC(60,40), it doesn't fit into DECIMAL,
but it fits into MEMO and VARCHAR.
Using the current switch, the user could either keep it as default
or cast it to anything else. That feature would be VERY complete then.
Best regards,
Tobias
| From | Date | Subject | |
|---|---|---|---|
| Next Message | BGoebel | 2018-06-04 14:38:22 | psqlodbc driver issue with Win10 Update 1803 |
| Previous Message | Tom Goodman | 2018-05-31 16:52:03 | Re: VB6 ODBC |