I can confirm this is fixed in current sources. Thanks for the report.
---
> #create table t (v varchar);
> #insert into t values ('0123456789a0123456789b0123456789c0123456789d');
>
> #select v from t;
>
>
Thomas Lockhart <[EMAIL PROTECTED]> 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 p
> Thomas Lockhart <[EMAIL PROTECTED]> 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 *real
...
> 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
Thomas Lockhart <[EMAIL PROTECTED]> 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 c
...
> 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
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Looking at the explain verbose output, it looks like it may be doing a
> conversion to name because it looks like there isn't a text(varchar),
> but there's a text(name) and a name(varchar). My guess is there's no
> text(varchar) because they're conside
> #select text(v) from t;
>
> text
> -
> 0123456789a0123456789b012345678
> (1 row)
>
> Truncation occurs.
Looking at the explain verbose output, it looks
like it may be doing a conversion to name because
it looks like there isn't a t
I can confirm this problem exists in current sources. Quite strange.
> #create table t (v varchar);
> #insert into t values ('0123456789a0123456789b0123456789c0123456789d');
>
> #select v from t;
>
> v
>
#create table t (v varchar);
#insert into t values ('0123456789a0123456789b0123456789c0123456789d');
#select v from t;
v
--
0123456789a0123456789b0123456789c0123456789d
(1 row)
So far, so good.
#select te
10 matches
Mail list logo
