| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
| Cc: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Dave Blasby <dblasby(at)refractions(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BUG: text(varchar) truncates at 31 bytes |
| Date: | 2001-10-04 02:47:28 |
| Message-ID: | 15539.1002163648@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)fourpalms(dot)org> writes:
>> Perhaps it'd be a better idea for the option of a freebie conversion
>> to be checked earlier, say immediately after we discover there is no
>> exact match for the function name and input type. Thomas, what do you
>> think?
> We *really* need that catalog lookup first. Otherwise, we will never be
> able to override the hardcoded compatibility assumptions in that
> matching routine.
Sure, I said *after* we fail to find an exact match. But the "freebie"
match is for a function name that matches a type name and is
binary-compatible with the source type. That's not a weak constraint.
ISTM that interpretation should take priority over interpretations that
involve more than one level of transformation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-10-04 03:05:16 | Re: Unicode combining characters |
| Previous Message | Tatsuo Ishii | 2001-10-04 02:16:42 | Re: Unicode combining characters |