Re: BUG: text(varchar) truncates at 31 bytes - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: BUG: text(varchar) truncates at 31 bytes
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4212758@m0114.s-mxs.net
Whole thread Raw
In response to BUG: text(varchar) truncates at 31 bytes  (Dave Blasby <dblasby@refractions.net>)
List pgsql-hackers
> Thomas Lockhart <lockhart@fourpalms.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.

That sounds very reasonable to me.

Andreas


pgsql-hackers by date:

Previous
From: Lincoln Yeoh
Date:
Subject: Re: Feature suggestion: Postgresql binding to one
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: Problem on AIX with current