RE: [HACKERS] SQL92

From: "Jackson, DeJuan" <djackson(at)cpsgroup(dot)com>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, jose(at)sferacarta(dot)com
Cc: lockhart(at)alumni(dot)caltech(dot)edu, pgsql-hackers(at)hub(dot)org
Subject: RE: [HACKERS] SQL92
Date: 1998-10-02 15:44:24
Message-ID: F10BB1FAF801D111829B0060971D839F447E09@cpsmail
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > The SQL92 LIKE:
> >
> > character-string-expression [NOT] LIKE pattern [ESCAPE
> > 'escape-char']
> >
> > allows only the special characters % and _
> >
> > You need The SQL3 SIMILAR
> >
> > character-string-expression [NOT] SIMILAR TO pattern [ESCAPE
> > 'escape-char']
> >
> > in this case pattern can involve additional special characters, not
> just
> > % and _ as in LIKE, but every regular expression or
> "[character_set]"
> > like you said. (Refer to "A Guide to SQL Standard 4th edition
> > Date-Rarwen, page 505).
> >
> > Jose'
> >
> >
>
> TODO item changed to:
>
> * add SIMILAR to allow character classes, 'pg_[a-c]%'
So are we going to add the character class support to LIKE or SIMILAR or
both? Just looking for clarification. Or are we going to use the regex
code for both?
-DEJ

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1998-10-02 15:45:06 Re: [HACKERS] Open 6.4 items
Previous Message Jackson, DeJuan 1998-10-02 15:41:09 RE: [HACKERS] SQL92