From: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
---|---|
To: | myaddress(at)gmx-topmail(dot)de |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: ODBC large binary data support |
Date: | 2017-01-09 13:25:47 |
Message-ID: | e8b8b420-0b63-bf8f-e842-02fb1cf67833@dream.email.ne.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi,
On 2017/01/09 20:41, myaddress(at)gmx-topmail(dot)de wrote:
> Dear Hiroshi Inoue,
> Just to avoid any confusion: I used the wrong sending e-mail address
> for my last answer. But it's the same person :-)
>
> It's working for the 64-bit version. Unfortunately, it's not working
> correctly for the 32-bit version. The problem is the last parameter of
> "SQLGetData". For the 32-bit version this is a pointer to a 32-bit
> signed integer (SQLLEN). This means, the integer overflows for large
> data >2 GB. I suggest to saturate the value for the 32-bit version and
> return 0x7fffffff in case the real value is bigger than that. Most
> applications just check if it's bigger than the provided buffer size
> and for that returning 0x7fffffff works fine. What do you think about it?
The problem might be avoided by using SQL_NO_TOTAL though I'm not sure.
Could you try the test drivers 9.5.0409 at
http://www.ne.jp/asahi/inocchichichi/entrance/psqlodbc/
?
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | myaddress | 2017-01-10 07:29:15 | Re: ODBC large binary data support |
Previous Message | myaddress | 2017-01-09 11:41:25 | Re: ODBC large binary data support |