Re: Modest proposal for making bpchar less inconsistent

2019-10-01 Thread Tom Lane
Kyotaro Horiguchi writes: > At Sat, 28 Sep 2019 08:22:22 -0400, Bruce Momjian wrote in > <2019092812.ga26...@momjian.us> >> On Fri, Sep 13, 2019 at 09:50:10PM +0200, Pavel Stehule wrote: >>> Dne pá 13. 9. 2019 16:43 uživatel Tom Lane napsal: It struck me that the real reason that we ke

Re: Modest proposal for making bpchar less inconsistent

2019-10-01 Thread Kyotaro Horiguchi
At Sat, 28 Sep 2019 08:22:22 -0400, Bruce Momjian wrote in <2019092812.ga26...@momjian.us> > On Fri, Sep 13, 2019 at 09:50:10PM +0200, Pavel Stehule wrote: > > > > > > Dne pá 13. 9. 2019 16:43 uživatel Tom Lane napsal: > > > > It struck me that the real reason that we keep getting gri

Re: Modest proposal for making bpchar less inconsistent

2019-09-28 Thread Bruce Momjian
On Fri, Sep 13, 2019 at 09:50:10PM +0200, Pavel Stehule wrote: > > > Dne pá 13. 9. 2019 16:43 uživatel Tom Lane napsal: > > It struck me that the real reason that we keep getting gripes about > the weird behavior of CHAR(n) is that these functions (and, hence, > their corresponding

Re: Modest proposal for making bpchar less inconsistent

2019-09-13 Thread Pavel Stehule
Dne pá 13. 9. 2019 16:43 uživatel Tom Lane napsal: > It struck me that the real reason that we keep getting gripes about > the weird behavior of CHAR(n) is that these functions (and, hence, > their corresponding operators) fail to obey the "trailing blanks > aren't significant" rule: > >

Modest proposal for making bpchar less inconsistent

2019-09-13 Thread Tom Lane
It struck me that the real reason that we keep getting gripes about the weird behavior of CHAR(n) is that these functions (and, hence, their corresponding operators) fail to obey the "trailing blanks aren't significant" rule: regprocedure|prosrc -