| From: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
|---|---|
| To: | Keith Handlon <Keith(dot)Handlon(at)sas(dot)com> |
| Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: SQL_QUERY_TIMEOUT |
| Date: | 2017-08-02 05:05:08 |
| Message-ID: | 5215542f-0f5e-b721-1d5e-0651e916692a@dream.email.ne.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi Keith,
On 2017/08/02 3:22, Keith Handlon wrote:
>
> When SQL_QUERY_TIMEOUT was added it was defined as SQLULEN as per the
> current ms odbc spec. But as of 3.5 wasn’t it a SQLUINTEGER?
>
Probably they were described when there was no 64bit ODBC.
SQLULEN == SQLUINTEGER on 32bit ODBC,
regards,
Hiroshi Inoue
> It looks like the majority of the other attributes like (SQL_NOSCAN,
> SQL_RETRIEVE_DATA, etc) are defined as SQLUINTEGER.
>
> This could cause a memory overwrite if its treated like an SQLUINTEGER
> like the other attributes.
>
> Thanks,
>
> Keith
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kazuki Uehara | 2017-08-02 07:47:24 | When doing installcheck, an error message "unresolved external symbol _get_test_dsn ..." displays. |
| Previous Message | Inoue, Hiroshi | 2017-08-02 04:32:31 | Re: ODBC application works while libpq fails |