Skip site navigation (1) Skip section navigation (2)

BUG #3092: character varying and integer cannot be matched

From: "Andrew Rass" <net-flight(at)gmx(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3092: character varying and integer cannot be matched
Date: 2007-03-01 10:20:17
Message-ID: 200703011020.l21AKHYO075157@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      3092
Logged by:          Andrew Rass
Email address:      net-flight(at)gmx(dot)net
PostgreSQL version: 8.2.3
Operating system:   FreeBSD 6.2
Description:        character varying and integer cannot be matched
Details: 

Hello the following problem has occured,

SELECT T055.MESOPRIM,T051.MESOPRIM FROM T055 T055,T051 T051
WHERE T055.MESOYEAR = 1278 AND T055.MESOCOMP = '1ZAP'
AND T051.MESOYEAR = 1278 AND T051.MESOCOMP = '1ZAP'
AND ( T055.C002 = T051.C001 AND T055.C004 IN (2,3)
AND lower(t051.c052)  LIKE '%frankfurt%' )ORDER BY T055.C002


ERROR: IN types character varying and integer cannot be matched
SQL Status:42804

mesoprim character varying(34);
mesoyear integer;
mesocomp character varying(4);
c002 character varying(20);
c001 character varying(20);

postgresql 7.4.7 did this
and now it did this problem like describe

thank you

Responses

pgsql-bugs by date

Next:From: Ilya StorozhilovDate: 2007-03-01 14:34:32
Subject: BUG #3093: Error with converting error messages between server and client encodings
Previous:From: Andrew WhiteDate: 2007-02-28 21:59:30
Subject: BUG #3089: View/Table Creation/Ownership Bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group