SQL_QUERY_TIMEOUT

From: Keith Handlon <Keith(dot)Handlon(at)sas(dot)com>
To: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: SQL_QUERY_TIMEOUT
Date: 2017-08-01 18:22:31
Message-ID: b19d33869457442faad80e7d73e65d55@MERCMBX49R.na.SAS.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

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?

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

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Igor Korot 2017-08-02 03:40:46 Re: ODBC application works while libpq fails
Previous Message Igor Korot 2017-07-31 13:05:37 ODBC application works while libpq fails