| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PATCH: CITEXT 2.0 v3 |
| Date: | 2008-07-09 20:50:44 |
| Message-ID: | BD40FA86-AD63-4331-96C8-EFD3F8E82C0B@kineticode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jul 9, 2008, at 13:40, Alvaro Herrera wrote:
> The problem is that we're in the middle of a commitfest, so
> everybody is
> busy reviewing other patches (in theory at least).
Of course.
> One thing that jumps at me is pgTAP usage, as Zdenek said. I
> understand
> that it's neat and all that, but we can't include the tests because
> they
> won't run unless one installs pgTAP which seems a nonstarter. So if
> you
> want the tests in the repository along the rest of the stuff, they
> really should use pg_regress.
It does use pg_regress. The test just load the included pgtap.sql file
to get the tap functions, and then away they go. If you run `make
installcheck` it works.
> It's not even difficult to use. Have a look at contrib/ltree/sql and
> contrib/ltree/expected for examples.
>
> If you want to push for pgTAP in core, that's fine, but it's a
> separate
> discussion.
Agreed. I've sent a couple of messages in a thread about that, the
latest this morning.
> The other possibility being, of course, that you are proposing
> citext to
> live on pgFoundry.
I'm not, actually. I mean, I have an updated version for 8.3, but it'd
be quite a pita to maintain them both, since the api for lowercasing
text is so much simpler in 8.4.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-07-09 21:01:03 | Re: PATCH: CITEXT 2.0 v3 |
| Previous Message | Martijn van Oosterhout | 2008-07-09 20:45:53 | Re: Summary of some postgres portability issues |