From: | Clemens Ladisch <clemens(at)ladisch(dot)de> |
---|---|
To: | pgsql-odbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: Bug report: x64 Row status Array uses wrong data type |
Date: | 2018-05-14 15:09:02 |
Message-ID: | f704455b-efcd-8e87-5a82-8709dfcd42c1@ladisch.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Jari Siikarla wrote:
> https://docs.microsoft.com/en-us/sql/odbc/reference/odbc-64-bit-information
> “
> SQLSetStmtAttr
> When the Attribute parameter has one of the following values, a 64-bit value is passed in *ValuePtr:
> …
> SQL_ATTR_ROW_STATUS_PTR
> …
> ”
This is a typo on that web page, "*ValuePtr" should be "ValuePtr". (Most
of these SQL_ATTR_xxx attribute values are not pointers, so it does not
make sense to dereference ValuePtr.)
Only the _pointer_ to the row status array is 64 bits.
> https://support.oracle.com/knowledge/Oracle%20Database%20Products/1472987_1.html
> “
> in 64-bit mode the status values are 64-bit
Of the two possible interpretations of Microsoft's statement, Oracle
chose the wrong one.
Regards,
Clemens
From | Date | Subject | |
---|---|---|---|
Next Message | Ashraf Parakkuth Thattasseri | 2018-05-15 04:49:49 | RE: 32-bit odbc source compilation failed |
Previous Message | Inoue, Hiroshi | 2018-05-14 14:13:50 | Re: 32-bit odbc source compilation failed |