"Dann Corbit" <[EMAIL PROTECTED]> writes:
> I guess that additional ambiguity arises if you add additional spaces to
> the end. Many database systems solve this by trimming the characters
> from the end of the string upon storage and the returned string will not
> have any trailing blanks.
Can you document that? ISTM that that would effectively make char(n)
and varchar(n) exactly equivalent, which is ... um ... a bit stupid.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
