Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g11D0Bl60998 for ; Fri, 1 Feb 2002 08:00:12 -0500 (EST) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.4/8.11.4) id g11CxG355544 for pgsql-sql@postgresql.org; Fri, 1 Feb 2002 07:59:16 -0500 (EST) (envelope-from news) From: "Tomas Eriksson" X-Newsgroups: comp.databases.postgresql.sql Subject: Compare with CHAR Date: Fri, 1 Feb 2002 13:59:08 +0100 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 13 Message-ID: X-Complaints-To: news@hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 To: pgsql-sql@postgresql.org X-Archive-Number: 200202/2 X-Sequence-Number: 6434 Hi. I'm using a table with a indexed CHAR(3)-column. When I use SELECT .. WHERE Col = 'XXX', some results are empty, but the value in the row seems to be correct like other rows. If I update the row with same data I can get it into the result. So I didn't find any logic reason for this. I can find all rows using LIKE (or with some substring tests) with no problems. Shouldn't = always works the same..? (Postgres 7.1.3) kind regards Tomas