Re: PATCH: CITEXT 2.0

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PATCH: CITEXT 2.0
Date: 2008-07-07 17:09:44
Message-ID: 2F472DC1-CB44-476C-ACFF-C2807C21751F@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 7, 2008, at 00:46, Zdenek Kotala wrote:

> You have to use varstr_cmp in citextcmp. Your code is correct,
> because for
> < <= >= > operators you need collation sensible function.
>
> You need to change only citext_cmp function to use strncmp() or call
> texteq function.

I'm confused. What's the difference between strncmp() and
varstr_cmp()? And why would I use one in one place and the other
elsewhere? Shouldn't they be used consistently?

> I'm think that this test will work correctly for en_US.UTF-8 at any
> time. I guess the test make sense only when Czech collation
> (cs_CZ.UTF-8) is selected, but unfortunately, you cannot change
> collation during your test :(.

No, I was wondering before what locale was used for initdb on the
build farm. I mean, how are locale-aware things really tested?

> I think, Best solution for now is to keep the test and add comment
> about recommended collation for this test.

Yep, that's what it does.

Thanks,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-07-07 17:20:03 Re: PATCH: CITEXT 2.0 v2
Previous Message Simon Riggs 2008-07-07 17:03:15 Re: Auto-explain patch