Re: Why format() adds double quote?

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: pavel(dot)stehule(at)gmail(dot)com
Cc: daniel(at)manitou-mail(dot)org, listas(at)guedesoft(dot)net, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why format() adds double quote?
Date: 2016-01-27 07:25:56
Message-ID: 20160127.162556.1164789055556324611.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> What do you exactly propose regarding white chars and multibyte chars
>> here? Maybe you propose to consider non ASCII white spaces (treate
>> them as ASCII white spaces)?
>>
>
> I propose the work with UTF white chars should be same like ASCII white
> chars. The current design is too simple - with possible pretty bad issues.
> Daniel's example is good - there is big gap in design.

I think we should consider followings before going forward:

1) Does PostgreSQL treat non ASCII white spaces same as ASCII white
spaces anyware in the system? If not, there's no reason we should
think format() and quote_indent() are exception.

2) What does the SQL standard say? Do they say that non ASCII white
spaces should be treated as ASCII white spaces?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-01-27 07:36:37 Re: Why format() adds double quote?
Previous Message Pavel Stehule 2016-01-27 07:06:13 Re: Why format() adds double quote?