On 5/2/2017 11:41 AM, Tom Lane wrote:
John R Pierce writes:
I thought Postgres supported client_encodings of BIG5, GB18030, and GBK,
all of which can be stored in the server using either UTF8 or
MULE_INTERNAL (MultiLingual EMACS) encodings for internal storage ?
Hm, there's MULE<=>BIG5 convert
John R Pierce writes:
> I thought Postgres supported client_encodings of BIG5, GB18030, and GBK,
> all of which can be stored in the server using either UTF8 or
> MULE_INTERNAL (MultiLingual EMACS) encodings for internal storage ?
Hm, there's MULE<=>BIG5 converters but I don't see any for GBK o
"Martel, Hong" writes:
> As I understand, currently Postgres doesn$B!G(Bt support Chinese encoding
> GBK and BIG5 on both server and client side, only UNICODE. Is it true? Are
> there any plans for postgresql team to implement GBK and BIG5 encoding
> anytime soon?
Yes, and no. There's bas
On 4/28/2017 7:45 AM, Martel, Hong wrote:
As I understand, currently Postgres doesn’t support Chinese encoding
GBK and BIG5 on both server and client side, only UNICODE. Is it
true? Are there any plans for postgresql team to implement GBK and
BIG5 encoding anytime soon?
Are there any alte
Hi,
As I understand, currently Postgres doesn’t support Chinese encoding GBK and
BIG5 on both server and client side, only UNICODE. Is it true? Are there any
plans for postgresql team to implement GBK and BIG5 encoding anytime soon?
Are there any alternative solutions for this besides switchi
