| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Igor Korot <ikorot01(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PQexecPrepared() question |
| Date: | 2025-12-22 08:18:57 |
| Message-ID: | 61e006772d8f0d8fb461d2da59b4f31ca22f4733.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2025-12-21 at 11:44 -0800, Igor Korot wrote:
> Adding following code:
>
> SQLHSTMT stmt;
> SQLWCHAR value[25];
> ret = SQLAllocHandle( SQL_HANDLE_STMT, m_hdbc, &stmt );
> ret = SQLExecDirect( stmt, L"SHOW client_encoding", SQL_NTS );
> ret = SQLBindCol( stmt, 1, SQL_C_WCHAR, &value, 25, 0 );
> ret = SQLFetch( stmt );
> ret = SQLFreeHandle( SQL_HANDLE_STMT, stmt );
>
> the value of the "value" variable is still "UTF8".
The ODBC driver comes in a "unicode" and an "ANSI" flavor.
If you are using the "unicode" driver, it will always set the
client encoding to UTF8.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2025-12-22 09:55:16 | Re: PQexecPrepared() question |
| Previous Message | Igor Korot | 2025-12-22 01:30:38 | Re: PQexecPrepared() question |