You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because MariaDB 10.7 has renamed utf8 to utf8mb3 (wich is the real econding name, also supported by MySQL), iconv.decode() function fails when utf8mb3 is passed as encoding (second parameter) when parsing BLOB columns.
Error: Encoding not recognized: 'utf8mb3' (searched as: 'utf8mb3')
at Object.getCodec (iconv-lite/lib/index.js:104:23)
at Object.getDecoder (iconv-lite/lib/index.js:125:23)
at Object.decode (iconv-lite/lib/index.js:38:25)
at Object.readMysqlValue (zongji/lib/common.js:470:23)
...
The text was updated successfully, but these errors were encountered:
juan-ferrer-toribio
changed the title
Crash when parsing utf8mb3 BLOB columns (MariaDB)
Crash when parsing utf8mb3 BLOB columns (MariaDB) Tag: v0.5.1
Aug 15, 2022
juan-ferrer-toribio
changed the title
Crash when parsing utf8mb3 BLOB columns (MariaDB) Tag: v0.5.1
Crash when parsing utf8mb3 BLOB columns (MariaDB 10.7) Tag: v0.5.1
Aug 15, 2022
Because MariaDB 10.7 has renamed utf8 to utf8mb3 (wich is the real econding name, also supported by MySQL),
iconv.decode()
function fails when utf8mb3 is passed as encoding (second parameter) when parsing BLOB columns.The text was updated successfully, but these errors were encountered: