Am 22.03.2023 um 20:48 schrieb Volker Hilsheimer:
Indeed, the many hits in the sql code are mostly from warning output, thanks
for checking.
But that Postgres supports UTF-8 doesn’t mean that an existing server is also
configured to use it. If a server is configured to work with e.g. ISO_8859_5
encoding, because all Qt clients (which are likely middleware servers, so fully
controlled) run on Windows machines with a corresponding code page, then Qt
deciding to encode in UTF-8 instead will break things, won’t it? And SQL is
just one example.
No, the client encoding is completely unrelated to the encoding on the
server and the database. All three can differ. Even informix supported
this already 15 years ago iirc. The conversion happens between the
client and server.
Christian
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
