From: | myaddress(at)gmx-topmail(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-10 07:29:15 |
Message-ID: | trinity-9133d25e-67d5-4a5e-96b0-40fc748215a0-1484033355550@3capp-gmx-bs27 |
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 class="signature">Dear Hiroshi Inoue,</div>
<div class="signature"> </div>
<div class="signature">The new update fixed my issues. It's also working with the 32-bit version now. The Microsoft documentation concerning SQL_NO_TOTAL is a little bit strange in my eyes. So, I don't know what the "correct" behavior is for the 32-bit version and data >2GB. My feeling teels me that SQL_NO_TOTAL is "correcter" than 0x7fffffff. So I'd say the current version is good.</div>
<div class="signature">When will you officially release it?</div>
<div class="signature"> </div>
<div class="signature">Thank you very much.</div></div></body></html>
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/html | 769 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Inoue, Hiroshi | 2017-01-11 12:17:44 | Re: ODBC large binary data support |
Previous Message | Inoue, Hiroshi | 2017-01-09 13:25:47 | Re: ODBC large binary data support |