From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | djackson(at)cpsgroup(dot)com (Jackson, DeJuan) |
Cc: | jose(at)sferacarta(dot)com, lockhart(at)alumni(dot)caltech(dot)edu, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] SQL92 |
Date: | 1998-10-02 16:09:06 |
Message-ID: | 199810021609.MAA09974@candle.pha.pa.us |
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?
No idea. It is just a valid TODO item.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-10-02 16:17:05 | Re: SGI Port of Postgresql 6.4 snapshot of 09/28/98 |
Previous Message | Bruce Momjian | 1998-10-02 16:05:14 | Re: [HACKERS] SQL92 |