From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PATCH: CITEXT 2.0 v3 |
Date: | 2008-07-14 17:36:48 |
Message-ID: | 14C29177-1351-4A8B-A840-099C0EC14E49@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 14, 2008, at 06:05, Andrew Dunstan wrote:
> You can certainly add any tests you like. But the buildfarm does all
> its regression tests using an install done with --no-locale. Any
> test that requires some locale to work, or make sense, should
> probably not be in your Makefile's REGRESS target.
Well, unless the display of the characters would be broken (the build
farm databases use UTF-8, no?), the output would look like this, which
should more or less work (I'm hoping):
SELECT citext_larger( 'Â'::citext, 'ç'::citext ) = 'ç' AS t WHERE
false and test_multibyte();
t
---
(0 rows)
> Some time ago I raised the question of doing locale- and encoding-
> aware regression tests, and IIRC the consensus seemed to be that it
> was not worth the effort, but maybe we need to revisit that. We
> certainly seem to be doing a lot more work now to get Postgres to
> where it needs to be w.r.t. locale support, and we've cleaned up a
> lot of the encoding issues we had, so maybe we need to reflect that
> in our testing regime more.
Makes sense to me.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2008-07-14 17:48:44 | Re: PATCH: CITEXT 2.0 v3 |
Previous Message | David E. Wheeler | 2008-07-14 17:33:21 | Re: Fwd: Proposal - UUID data type |