upgrading postgresql broke some queries

From: Aras Angelo <araskoktas(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: upgrading postgresql broke some queries
Date: 2009-08-04 19:02:58
Message-ID: 5136d4130908041202t6b8a5335nff897002f77c2cff@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2009-08-04 19:13:34 Re: RAID for the DB filesystem
Previous Message Shane Ambler 2009-08-04 16:59:06 Schema migration-cvs