upgrading postgresql broke some queries - Mailing list pgsql-admin

From Aras Angelo
Subject upgrading postgresql broke some queries
Date
Msg-id 5136d4130908041202t6b8a5335nff897002f77c2cff@mail.gmail.com
Whole thread Raw
Responses Re: upgrading postgresql broke some queries  (Devrim GÜNDÜZ <devrim@gunduz.org>)
Re: upgrading postgresql broke some queries  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-admin
Hi All,

I recently upgraded my box to the latest version. The  previous one was a bit outdated. Apparently we have some bad structure formatting in our db design, cause the latest version broke our software. The issue is some character varying fields are used in queries joining to integers. The old db server was just allowing us to join INT to CHAR. Now its not. I researched on some ways to fix this, i can do CAST(field AS text) in my queries, but there are dozens and they are hard to find.

I was wondering if there is an easy global solution for this. I cant just alter the CHAR fields to INT because some rows have empty values. I can just change them to 'zero' and alter type to integer but im worried i can lose some functionality because some queries again is looking for empty value.

thanks

pgsql-admin by date:

Previous
From: Shane Ambler
Date:
Subject: Schema migration-cvs
Next
From: Scott Marlowe
Date:
Subject: Re: RAID for the DB filesystem