Re: Postgre RAISE NOTICE and PHP

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "Randal L(dot) Schwartz" <merlyn(at)stonehenge(dot)com>
Cc: Clemens Schwaighofer <clemens_schwaighofer(at)e-gra(dot)co(dot)jp>, Andre Lopes <lopes80andre(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Postgre RAISE NOTICE and PHP
Date: 2009-08-19 17:57:45
Message-ID: dcc563d10908191057m7cfb8322rfff93646184ae503@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Aug 19, 2009 at 8:41 AM, Randal L.
Schwartz<merlyn(at)stonehenge(dot)com> wrote:
>>>>>> "Clemens" == Clemens Schwaighofer <clemens_schwaighofer(at)e-gra(dot)co(dot)jp> writes:
>
> Clemens> Just in my opinion, this regex is completely too large. For basic
> Clemens> validating something like:
> Clemens> ^[A-Za-z0-9!#$%&'*+-\/=?^_`{|}~][A-Za-z0-9!#$%&'*+-\/=?^_`{|}~\.]{0,63}(at)[a-zA-Z0-9-]+(\.[a-zA-Z0-9-]{1,})*\.([a-zA-Z]{2,4}){1}$
> Clemens> works very well
>
> Fails on ".mobile" TLD.  Has a pointless {1} in it, which does
> absolutely nothing, providing that the creator of the regex was already
> missing a few clues.

Remonds me of the saying that for every complex problem there is a
simple, elegant and incorrect solution.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-08-19 18:09:59 Re: pg_restore returns always error if backup is greater than 2 GB
Previous Message Glen Jarvis 2009-08-19 17:51:56 Re: Changing owner of pg_toast tables