RE: [suggestion]support UNICODE host variables in ECPG

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: "Nagaura, Ryohei" <nagaura(dot)ryohei(at)jp(dot)fujitsu(dot)com>
Cc: "'jingwangian(at)gmail(dot)com'" <jingwangian(at)gmail(dot)com>, "'michael(dot)paquier(at)gmail(dot)com'" <michael(dot)paquier(at)gmail(dot)com>, "'meskes(at)postgresql(dot)org'" <meskes(at)postgresql(dot)org>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: [suggestion]support UNICODE host variables in ECPG
Date: 2018-12-18 02:13:11
Message-ID: 0A3221C70F24FB45833433255569204D1FB42AB5@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Nagaura, Ryohei [mailto:nagaura(dot)ryohei(at)jp(dot)fujitsu(dot)com]
> There is a demand for ECPG to support UNICODE host variables.
> This topic has also appeared in thread [1].
> I would like to discuss whether to support in postgres.
>
> Do you have any opinion?

* What's the benefit of supporting UTF16 in host variables?
* Does your proposal comply with the SQL standard? If not, what does the SQL standard say about support for UTF16?
* Why only Windows?

Regards
Takayuki Tsunakawa

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2018-12-18 02:24:37 Re: Proving IS NOT NULL inference for ScalarArrayOpExpr's
Previous Message Tom Lane 2018-12-18 01:58:44 Re: 'infinity'::Interval should be added