Skip site navigation (1) Skip section navigation (2)

Re: writing new regexp functions

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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!

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2007-02-03 02:08:56
Subject: Re: Dirty pages in freelist cause WAL stuck
Previous:From: Tom LaneDate: 2007-02-03 01:56:31
Subject: Re: writing new regexp functions

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-02-03 02:44:27
Subject: Re: [HACKERS] unixware and --with-ldap
Previous:From: Tom LaneDate: 2007-02-03 01:56:31
Subject: Re: writing new regexp functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group