From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: length coerce for bpchar is broken since 7.0 |
Date: | 2000-10-17 22:57:26 |
Message-ID: | 20001018075726W.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > I'm going to fix the problem by changing bpcharin() rather than
> > changing exprTypmod(). Surely we could fix the problem by changing
> > exprTypmod() for INSERT, however, we could not fix the similar problem
> > for COPY FROM in the same way. Changing bpcharin() would solve
> > problems of both INSERT and COPY FROM. So bpcharin() seems more
> > appropreate place to fix both problems.
>
> bpcharin() will most definitely NOT fix the problem, because it often
> will not know the target column's typmod, if indeed there is an
> identifiable target column at all.
Can you give me any example for this case?
> I agree that it's a good solution
> for COPY FROM, but you need to fix exprTypmod() too.
Anyway, I'm gotoing to fix exprTypmod() also.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-10-17 23:36:27 | Re: length coerce for bpchar is broken since 7.0 |
Previous Message | Nishad Prakash | 2000-10-17 20:51:09 | Re: UPPER and LOWER dosen't work correctly on special caracters (umlauts) |