May I ask why our ybdb does not support GB18030? What is the unsupported background? What modifications are needed to support it?
Hi! Are you asking for GB18030 to be the default encoding for a database? Note that this is not support by Postgres, which the YugabyteDB YSQL API is compatible with.
postgres=# CREATE DATABASE test WITH encoding gb18030; ERROR: gb18030 is not a valid encoding name
yugabyte=# CREATE DATABASE test WITH encoding gb18030; ERROR: gb18030 is not a valid encoding name LINE 1: CREATE DATABASE test WITH encoding gb18030
Are you asking about the conversion functions or \encoding?
I just want YugabyteDB to support GB18030 encoding, so that the data for read and write operations is compatible with GB18030 encoding format.
Ok. I was looking into this for you and found that enabling conversions is on our longer-term plan for full PG compatibility, but not planned in our short-term roadmap. But I will make your request known and will update this thread when the functionality is available.
@Jim_Knicely do we have a github issue for this?