From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why format() adds double quote? |
Date: | 2016-01-27 07:36:37 |
Message-ID: | CAFj8pRBusukC+-P05iK91dF4-LdUc+YFhv+UQ3mkQSYBxcbXjg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2016-01-27 8:25 GMT+01:00 Tatsuo Ishii <ishii(at)postgresql(dot)org>:
> >> 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.
>
+1
>
> 2) What does the SQL standard say? Do they say that non ASCII white
> spaces should be treated as ASCII white spaces?
>
I am not sure, if SQL standard say some about it. But I am sure, so using
unescaped or unclosed UTF8 spaces is bug, dangerous, wrong
Pavel
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2016-01-27 07:42:22 | Re: Existence check for suitable index in advance when concurrently refreshing. |
Previous Message | Tatsuo Ishii | 2016-01-27 07:25:56 | Re: Why format() adds double quote? |