From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jeremy Drake <pgsql(at)jdrake(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: writing new regexp functions |
Date: | 2007-02-03 02:03:13 |
Message-ID: | 20070203020313.GA27022@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Fri, Feb 02, 2007 at 08:56:31PM -0500, Tom Lane wrote:
> Jeremy Drake <pgsql(at)jdrake(dot)com> writes:
> > I want to ask, should I break with following substring's
> > precedent, and put the pattern first (as most people probably
> > would expect), or should I break with perl's precedent and put the
> > pattern second (to behave like substring)?
>
> All of SQL's pattern match operators have the pattern on the right,
> so my advice is to stick with that and try not to think about Perl
> ;-)
Perl provides inspiration, but here, consistency would help more than
orderly imitation of how it does what it does. And besides, when
people really need Perl, they can pull it in as a PL :)
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-02-03 02:08:56 | Re: Dirty pages in freelist cause WAL stuck |
Previous Message | Tom Lane | 2007-02-03 01:56:31 | Re: writing new regexp functions |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-02-03 02:44:27 | Re: [HACKERS] unixware and --with-ldap |
Previous Message | Tom Lane | 2007-02-03 01:56:31 | Re: writing new regexp functions |