RE: [HACKERS] SQL92 - Mailing list pgsql-hackers

From Jackson, DeJuan
Subject RE: [HACKERS] SQL92
Date
Msg-id F10BB1FAF801D111829B0060971D839F447E09@cpsmail
Whole thread Raw
Responses Re: [HACKERS] SQL92
List 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

pgsql-hackers by date:

Previous
From: "Jackson, DeJuan"
Date:
Subject: RE: [HACKERS] SQL92
Next
From: Bernhard Lorenz
Date:
Subject: indices: ~* / text_ops