Re: [HACKERS] lower() broken?

> > Vince> Oops! Yeah, I guess lower wouldn't work so well if it was
> > Vince> a numeric field. Anyway, username is a char(8).
> > It won't be equal to 'joblo', it will be equal to 'joblo '. You
> > may want to consider using varchar(8).
> Damn. That's the one thing that never even occurred to me!

I don't remember what my old Ingres system did for comparisons of char
against other string types; does every system (or the SQL standard)
consider the trailing blanks significant, or should they be implicitly
ignored in comparisons?

btw, if you don't want to redefine the column, then try

where trim(trailing from username) = lower('joblo');

but that will be a slower query since "username" must be trimmed before
comparison.

- Tom