[DiscordArchive] what charset must been set for guaranteed writing and reading of the correct value ?
[DiscordArchive] what charset must been set for guaranteed writing and reading of the correct value ?
Original source
what charset must been set for guaranteed writing and reading of the correct value ?
rektbyfaith
02-02-2022, 01:14 PM #1Archived author: Bogir • Posted: 2022-02-02T13:14:51.583000+00:00
Original source
what charset must been set for guaranteed writing and reading of the correct value ?
Original source
from time to time I register new accounts and can't login to them if I used utf8 or utf8mb4.
rektbyfaith
02-02-2022, 01:17 PM #2Archived author: Bogir • Posted: 2022-02-02T13:17:04.812000+00:00
Original source
from time to time I register new accounts and can't login to them if I used utf8 or utf8mb4.
Original source
now I set latin1 befor transaction and it seems that this fixed the situation.
I'm not seen description about it on wiki
rektbyfaith
02-02-2022, 01:18 PM #3Archived author: Bogir • Posted: 2022-02-02T13:18:47.408000+00:00
Original source
now I set latin1 befor transaction and it seems that this fixed the situation.
I'm not seen description about it on wiki
Original source
utf8mb3 (previously utf8_general) is default on mysql, it used 3 bytes for utf8 format, it been splitted within mariadb 10.4+ versions where utf8mb4 uses 4 bytes and to utf8mb3 which uses previous range (3 bytes)
rektbyfaith
02-02-2022, 01:22 PM #4Archived author: andriuspel • Posted: 2022-02-02T13:22:42.865000+00:00
Original source
utf8mb3 (previously utf8_general) is default on mysql, it used 3 bytes for utf8 format, it been splitted within mariadb 10.4+ versions where utf8mb4 uses 4 bytes and to utf8mb3 which uses previous range (3 bytes)
Original source
utf8mb3 based queries, datas are fine with utf8mb4 but utf8mb4 based range is not compatible to utf8mb3 if data takes all 4 byte characters range
rektbyfaith
02-02-2022, 01:24 PM #5Archived author: andriuspel • Posted: 2022-02-02T13:24:48.804000+00:00
Original source
utf8mb3 based queries, datas are fine with utf8mb4 but utf8mb4 based range is not compatible to utf8mb3 if data takes all 4 byte characters range
Original source
i mean, utf8mb3 -> utf8mb4 (OK)
utf8mb4 -> utf8mb3 (potentially compatible if data doesn;t takes whole 4 bytes range)
rektbyfaith
02-02-2022, 01:26 PM #6Archived author: andriuspel • Posted: 2022-02-02T13:26:12.075000+00:00
Original source
i mean, utf8mb3 -> utf8mb4 (OK)
utf8mb4 -> utf8mb3 (potentially compatible if data doesn;t takes whole 4 bytes range)
Original source
but yet older applications compiled within mysql version package may could work wrong with these two types, for example, spellwork application.
rektbyfaith
02-02-2022, 01:41 PM #7Archived author: andriuspel • Posted: 2022-02-02T13:41:15.099000+00:00
Original source
but yet older applications compiled within mysql version package may could work wrong with these two types, for example, spellwork application.