Date: Sat, 24 Aug 2002 23:27:30 -0500
From: "Ross J. Reedstrom" <reedstrm@rice.edu>
To: Jiaqing Wang <jjw72@swbell.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: weird situation, BUG or I'm not doing it right
Message-ID: <20020825042730.GA6376@rice.edu>
Mail-Followup-To: "Ross J. Reedstrom" <reedstrm@ece.rice.edu>,
	Jiaqing Wang <jjw72@swbell.net>, pgsql-sql@postgresql.org
References: <KCEJKHPEBJGGCDBEMMNKIEGCCBAA.jjw72@swbell.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <KCEJKHPEBJGGCDBEMMNKIEGCCBAA.jjw72@swbell.net>
User-Agent: Mutt/1.3.27i

On Sat, Aug 24, 2002 at 10:56:31PM -0700, Jiaqing Wang wrote:
> Hello,
> 
> I found below situation weird, it seems to me a bug.
> 
> backend=> select * from valid_addr where state_abrev=upper('pr');
>  zip_code | city_name | state_abrev
> ----------+-----------+-------------
> (0 rows)
> 
> while "select * from valid_addr where state_abrev='PR';" produces following
> output
> 
<20 lines of output>

You left out the critical piece: what's the schema for the table valid_addr?
I'll deduce that the column "state_abrev" is defined as something like
'char(4)'. It needs to be either char(2) (if _all_ state abbreviations are 
guarenteed to be only 2) or as text. fixed with char fields are padded with
blanks. Not a bug, but an feature of the SQL standard.

Ross