Joe Conway <[EMAIL PROTECTED]> writes:
> I stumbled across this behavior today and it seems strange if not a bug:
ascii() is defined as ascii(text). As of 7.4, bpchar->text conversion
strips trailing blanks, so what ascii() sees is a zero-length string.
Given that trailing blanks are insignificant in bpchar, I'm not sure I'd
call this a bug. If we decide it is, we could work around it by
creating an ascii(bpchar) entry ... but what's the argument that says
insignificant trailing blanks must map to the same thing as significant
blanks?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
