| 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 22:08:49 |
| Message-ID: | 2362.1002233329@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:
>> 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.
> Ah, OK I think. If there is a counterexample, it is probably no less
> obscure than this one.
Done. Essentially, this amounts to interchanging steps 2 and 3 of the
function call resolution rules described at
http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/typeconv-func.html
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-10-04 22:27:53 | Re: Plpython bug with int8 - Found, need advice |
| Previous Message | Serge Sozonoff | 2001-10-04 21:36:56 | OSX 10.1 |