| From: | "Volker Beck" <volker(dot)beck(at)gmx(dot)de> |
|---|---|
| To: | h-inoue(at)dream(dot)email(dot)ne(dot)jp |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: ODBC large binary data support |
| Date: | 2017-01-09 11:38:37 |
| Message-ID: | trinity-b0ddd448-70ce-460f-aebd-028faca0c992-1483961917243@3capp-gmx-bs72 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Dear Hiroshi Inoue,
<div> </div>
<div>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?</div>
<div>Thanks a lot!</div>
</div></div></body></html>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 770 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | myaddress | 2017-01-09 11:41:25 | Re: ODBC large binary data support |
| Previous Message | Inoue, Hiroshi | 2017-01-08 12:22:22 | Re: ODBC large binary data support |