MIME-Version: 1.0
References: <9a0ce31a49f149d8d982d2b359095560655f781e.camel@cybertec.at>
 <CA+FnnTzE34VJWR7xkymaKEwXiiQ8j3o03m0+qcQsRr2JkRQLwQ@mail.gmail.com>
 <ebaca1066dfdf567d158fc48dce86a6fcc132988.camel@cybertec.at>
 <CA+FnnTz5tcJEL12ir1nxe9q75rxaAdfBtcFUNiD4R5gW_JR23A@mail.gmail.com>
 <CA+FnnTyYBNwbzFs5GqO+SMg3g60jPTsnmFwTV=_s_YboGo-68A@mail.gmail.com>
 <852dee881b6cc82b9d4b51d69d48c415e2a87b4d.camel@cybertec.at>
 <CA+FnnTwtd-YJo5zp3obQer3qfbacg5s-4b3+5PvUkL3e+5Eh4Q@mail.gmail.com>
 <61121.1766295563@sss.pgh.pa.us> <6uz5ppdgqhlovw3df2dmzgzrfbfmmy5pys37ln7u4kyidaftgo@gxgkvkbwk3zh>
 <CA+FnnTxVZ64Lrq3t35j7w8mE=oP94TgetT62+Y8=ea_VfE2uEw@mail.gmail.com> <47v26pfhc2hnz3ax2u6ogke7npeyghbkxghov5hysv2f7ttchs@c5vrfavj7oqe>
In-Reply-To: <47v26pfhc2hnz3ax2u6ogke7npeyghbkxghov5hysv2f7ttchs@c5vrfavj7oqe>
From: Igor Korot <ikorot01@gmail.com>
Date: Mon, 22 Dec 2025 15:07:52 -0800
Message-ID: <CA+FnnTwz2PSSi2MVoH3rCKtAn=beRm97m7nGyxX1d3oF5EFVkw@mail.gmail.com>
Subject: Re: PQexecPrepared() question
To: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BFnnTwz2PSSi2MVoH3rCKtAn%3DbeRm97m7nGyxX1d3oF5EFVkw%40mail.gmail.com>
Precedence: bulk

Hi, Peter,

On Mon, Dec 22, 2025 at 1:55=E2=80=AFAM Peter J. Holzer <hjp-pgsql@hjp.at> =
wrote:
>
> On 2025-12-21 17:30:38 -0800, Igor Korot wrote:
> > On Sun, Dec 21, 2025 at 1:19=E2=80=AFPM Peter J. Holzer <hjp-pgsql@hjp.=
at> wrote:
> > > As I see it, Igor has two options:
> > >
> > > 1) Send UTF8. wcstombs is the wrong tool for this, since it uses the
> > >    current locale which is obviously not using UTF-8. I don't program=
 in
> > >    C++, but I'm pretty sure there is a portable way to encode a strin=
g
> > >    in UTF-8.
> [...]
> > > I think 1) is the better strategy, but them I've been a UTF-8 fan-boy
> > > for over 30 years ;-).
> >
> > Maybe all I need is something like this:
> >
> > convert(char *dest, const std::wstring src)
> > {
> >     const wchar_t *temp =3D src.c_str();
> >     while( *dest )
> >     {
> >         dest++;
> >     }
> >     while( *temp )
> >     {
> >         *dest =3D *temp;
> >         dest++;
> >         temp++;
> >     }
> >     *dest++ =3D '\0';
> >     *dest =3D '\0';
> > }
> >
> > ?
>
> I hope your compiler complains loudly about that code. You can't just
> assign a wchar_t to a char and expect it to do anything sensible.

At least MSVC 2017 did not.
However, trying didn't solve it. Same error.

>
> A short search points to std::wstring_convert, but that has been
> deprecated in C++17, and it's not obvious to me what the replacement is.
>
> There is always ICU, of course, but that feels like cracking a nut with
> a sledgehammer.

I think ICU IS a replacement for wstring_comvert.
Will check it.

>
> Personally, I might roll my own if an hour of googling doesn't turn up
> anything promising (UTF-8 encoding is quite simple), but that shouldn't
> be necessary.
>
>
>         hjp
>
> --
>    _  | Peter J. Holzer    | Story must make more sense than reality.
> |_|_) |                    |
> | |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
> __/   | http://www.hjp.at/ |       challenge!"