Re: SQLGetConnectAttrW + SQL_ATTR_CURRENT_CATALOG => wrong byte count?

From: "Inoue,Hiroshi" <hinoue205(at)gmail(dot)com>
To: Marsupilami79 <marsupilami79(at)gmx(dot)de>
Cc: pgsql-odbc(at)lists(dot)postgresql(dot)org
Subject: Re: SQLGetConnectAttrW + SQL_ATTR_CURRENT_CATALOG => wrong byte count?
Date: 2022-11-30 11:19:52
Message-ID: CAFGcedVioNNaedu4fiCFNOL=7LKC41gf5eWgDCz3CHd-CL8K3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hi Jan,

The psqlodbc unicode driver correctly returns the number of bytes(10 bytes
for a database name "visco") here.

regards,
Hiroshi Inoue

2022年11月23日(水) 0:57 Marsupilami79 <marsupilami79(at)gmx(dot)de>:

> Hello,
>
> I am a co author of a data access library and we recently added an ODBC
> bridge. This bridge has the capability to detemine the current Catalog /
> Database. This is done by calling SQLGetConnectAttrW.
>
> We try to determine the size of the buffer that is needed for the
> catalog name in the following manner:
> SQLGetConnectAttrW(fHDBC, SQL_ATTR_CURRENT_CATALOG, null, 0, &aLen)
>
> The ODBC driver for Microsoft SQL server correctly returns the number of
> bytes required (10 bytes for the Database name "Stork") in the aLen
> parameter. The ODBC driver for PostgreSQL returns the number of
> characters (8 characters for a database named "topsales"), where it
> should return 16 for the number of bytes required.
>
> I tested this with the psqlodbc_13_02_0000-x86 download for Windows 10
> and installed the Unicode ODBC driver.
>
> I assume this is a bug and needs to be fixed. I just don't know if this
> is the right place to report the bug to?
>
> With best regards,
>
> Jan
>
>
>

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Inoue,Hiroshi 2022-12-01 05:59:42 Re: [ Bug Report ]Re: column_query buffer in PGAPI ColumnPrivileges
Previous Message Jon Raiford 2022-11-28 14:01:54 Re: SQLGetConnectAttrW + SQL_ATTR_CURRENT_CATALOG => wrong byte count?