> > If VARSIZE returned from exprTypmod() and atttypmod passed to > > coerce_type_typmod() is equal, the function node to call bpchar() > > would not be added. > > Um, what's wrong with that? Seems to me that parse_coerce is doing > exactly what it's supposed to, ie, adding only length coercions > that are needed. Simply clipping multibyte strings by atttypmode might produce incorrect multibyte strings. Consider a case inserting 3 multibyte letters (each consisting of 2 bytes) into a char(5) column. Or this kind of consideration should be in bpcharin() as I said in the earilier mail? -- Tatsuo Ishii
- [HACKERS] length coerce for bpchar is broken since 7.0 Tatsuo Ishii
- Re: [HACKERS] length coerce for bpchar is broken since ... Tom Lane
- Re: [HACKERS] length coerce for bpchar is broken si... Tatsuo Ishii
- Re: [HACKERS] length coerce for bpchar is broke... Tom Lane
- Re: [HACKERS] length coerce for bpchar is b... Tatsuo Ishii
- Re: [HACKERS] length coerce for bpchar... Tom Lane
- Re: [HACKERS] length coerce for bp... Tatsuo Ishii
- Re: [HACKERS] length coerce fo... Tom Lane
- Re: [HACKERS] length coerce fo... Tatsuo Ishii
- Re: [HACKERS] length coerce fo... Tom Lane
- Re: [HACKERS] length coerce fo... Tatsuo Ishii
- Re: [HACKERS] length coerce fo... Tom Lane
- Re: [HACKERS] length coerce for bpchar is broken since ... Bruce Momjian