| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Igor Korot <ikorot01(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PQexecPrepared() question |
| Date: | 2025-12-21 17:17:16 |
| Message-ID: | 138367.1766337436@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> It is not the same setup, in your original question you are hand writing
> code not running a script through the ODBC driver. Best bet is the ODBC
> driver is picking up the client(Windows) encoding and passing it to the
> server.
It might be the other way around. psql absolutely will try to infer
an encoding from its environment, but perhaps the ODBC driver does
not, or does it differently.
In any case, "SHOW client_encoding" in both the working and
non-working contexts would yield useful information.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Korot | 2025-12-21 19:44:49 | Re: PQexecPrepared() question |
| Previous Message | Igor Korot | 2025-12-21 16:58:07 | Re: PQexecPrepared() question |