| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LIKE, CHAR(), and trailing spaces |
| Date: | 2011-02-03 00:40:51 |
| Message-ID: | AANLkTikB9nbesPX7q-UDYNTQEU8qi3KGE=qzPMHRYRu+@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3 February 2011 10:54, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> It seems LIKE is considering the trailing CHAR(10) field spaces as
> significant, even though our documentations says:
>
-- snip --
>
> It says trailing spaces are not significant for character comparisons
> --- the real question is whether LIKE is a comparison. Obvioiusly '='
> is a comparison, but the system does not treat LIKE as a comparison in
> terms of trailing spaces. Is that desired behavior?
Interesting. I would have to say that from the user point of view,
LIKE is definitely a comparison, and if the rest of the operators on
bpchar ignore whitespace then LIKE ought to as well.
Is the situation the same for regex matches (~ operators)?
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-02-03 00:48:38 | Re: LIKE, CHAR(), and trailing spaces |
| Previous Message | Justin Pitts | 2011-02-03 00:29:20 | Re: [HACKERS] Slow count(*) again... |