Re: 8.3 vs 8.2 sql compatiblity issue - Mailing list pgsql-general

From Tom Lane
Subject Re: 8.3 vs 8.2 sql compatiblity issue
Date
Msg-id 7040.1195150640@sss.pgh.pa.us
Whole thread Raw
In response to Re: 8.3 vs 8.2 sql compatiblity issue  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: 8.3 vs 8.2 sql compatiblity issue  (Tony Caduto <tony_caduto@amsoftwaredesign.com>)
List pgsql-general
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Tony Caduto <tony_caduto@amsoftwaredesign.com> wrote:
>> I am actually getting a lot of these operator does not exist errors
>> in 8.3 another one I get is operator does not exist for char=integer

> This appears to be a classic example of:
> Casts to text that formerly occurred implicitly may now need to be
> written explicitly

That's no doubt got something to do with it, but I think Tony is mighty
confused about exactly what is failing.  pg_constraint.conkey is not
text, for instance; it's smallint[] and so the quoted bit should still
work just fine.  I'd suggest trying the query in some client that gives
you an error location pointer, which whatever he's using evidently does
not.

            regards, tom lane

pgsql-general by date:

Previous
From: "Garber, Mikhail"
Date:
Subject: Postgresql and resource isolation
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Postgresql and resource isolation