Re: maybe a bug in plpgsql, nulls and empty strings are not the same
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Domingo Alvarez Duarte <domingo@dad-it.com>
Cc: pgsql-hackers@postgresql.org
Date: 2001-05-28T16:02:48Z
Lists: pgsql-hackers
Domingo Alvarez Duarte <domingo@dad-it.com> writes: > When trying write a function in plpgsql I'm getting behavior that > probably isn't the corect one. It works as expected if you declare v_sep as varchar rather than char. I think plpgsql may be interpreting v_sep char; as declaring v_sep to be the internal 1-byte "char" type, not char(n) with unspecified length as you are expecting. There's definitely something strange going on with the assignment v_sep := ''''; In any case it's a tad bizarre to use char rather than varchar for something that you intend to have varying width, no? regards, tom lane