*On 17/11/16 08:06, Dimitry Sibiryakov wrote:*
> *17.11.2016 11:51, ML wrote: *
>> It looks like the driver does not populate its database name
>> attribute from the connection string.
> According to MSDN, it must not. But it must return SQL_NO_DATA.
> Register ticket in tracker, please.
Well that
17.11.2016 11:51, ML wrote:
> It looks like the driver does not populate its database name attribute from
> the connection
> string.
According to MSDN, it must not. But it must return SQL_NO_DATA. Register
ticket in
tracker, please.
--
WBR, SD.
*On 16/11/16 17:07, Dimitry Sibiryakov wrote:*
> *16.11.2016 20:32, d4t4f...@gmail.com wrote: *
>> I'm calling SQLGetConnectAttr() with the SQL_ATTR_CURRENT_CATALOG
>> attribute, but it does not seem to return anything meaningful.
> Do you check its return value? It must be SQL_NO_DATA if you didn
16.11.2016 20:32, d4t4f...@gmail.com wrote:
> I'm calling SQLGetConnectAttr() with the SQL_ATTR_CURRENT_CATALOG attribute,
> but it does
> not seem to return anything meaningful.
Do you check its return value? It must be SQL_NO_DATA if you didn't call
SQLSetConnectAttr() beforehand.
--
