Peter Eisentraut writes:
> On ons, 2011-03-09 at 18:07 -0500, Tom Lane wrote:
>> Now the downside of that is that a runtime failure won't give you an
>> parse error pointer to indicate which function is having trouble ...
>> but having an error pointer for an error that shouldn't be thrown in
>> t
On ons, 2011-03-09 at 18:07 -0500, Tom Lane wrote:
> The first of these errors is OK, but surely the second is not, because
> ||
> doesn't give a fig about collations. I think instead of this:
>
> /* XXX: If we knew which functions required collation
> information,
> * we could s
db1=# create table t1 (f1 text collate "aa_DJ.utf8",
f2 text collate "an_ES.utf8" );
CREATE TABLE
db1=# select f1 < f2 from t1;
ERROR: collation mismatch between implicit collations "aa_DJ.utf8" and
"an_ES.utf8"
LINE 1: select f1 < f2 from t1;
^
HINT: You can override the c
