Re: 8.3 vs 8.2 sql compatiblity issue

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 15 Nov 2007 12:03:27 -0600
Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)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

Data types other than char and varchar are no longer implicitly
castable to text, except in the limited case of a || (concatenation)
operator whose other input is textual. While this will require explicit
casts in a few queries that didn't need them before, the elimination of
surprising interpretations justifies it.

- From the release notes :)

http://www.postgresql.org/docs/8.3/static/release-8-3.html

Sincerely,

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHPIvRATb/zqfZUUQRAsmpAJ9pKOwl2K5sGtulosfEcZuuCLaFSACcDyk8
CXZQidZVUA3Wn7vzC02yB8g=
=/PEp
-----END PGP SIGNATURE-----