(Two answers) Three years ago
I might ask the same question again...
Last time was too bad at explaining, so I thought it wasn't conveyed to people watching what they wanted to do, so please let me know again.
I am connecting to an external server from my computer.
For external servers, postgresql and encoding is SQL_ASCII.
Since it is SQL_ASCII, the Japanese character code is stored in SJIS.
Probably because the default setting for Teraterm is UTF-8, it is garbled.
If you do not type set client_encoding to 'sjis' every time, Japanese will not be displayed.
I would like to check the Japanese language if I log in and do select*from table_name; instead of automatically set client....
I think the default setting should be sjis.
Is it really a term configuration problem?
set client_encoding to 'sjis'
This is a command to hit on the server being used, right?Does the server login user have a locale of ja_JP.UTF8 or something like that?And if you put the data in that database, what was the character code for autumn?
In other words, I wonder if the character code of the server locale and the data that postgres holds is unmatched and the result is "disguised."Of course, teraterm also has its own character code to use as a terminal setting...I think this is the cause if the server you are logged in to can be cured by the command.
I mean, I don't know how to say SJIS because it's SQL_ASCII.And SJIS is JIS90? MS932? Which one are you referring to?
© 2024 OneMinuteCode. All rights reserved.