Ryan Mahoney <[EMAIL PROTECTED]> writes:
>> Hmm ... evidently zipcode is declared as type char(5) (note the "bpchar"
>> coercion). Is the plpgsql variable it's being compared to declared the
>> same way? This could be ye olde cross-datatype-coercion problem.
> Interesting! I think in plpgsql the data type of the argument coming
> in to the function is "text".
Bingo.
> Are you suggesting that I:
> a. use a different datatype in plpgsql or
> b. cast the values or
> c. change the data type in the table
Yes ;-). Presumably (b) would be the least painful route, but any of
these would do the trick.
> I am not familiar with the bpchar type, but I am looking into it now.
Internal name for char(n).
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
