| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | t-ishii(at)sra(dot)co(dot)jp |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Constantin Teodorescu <teo(at)flex(dot)ro>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Broken select on regular expression !!! |
| Date: | 1999-05-21 05:52:16 |
| Message-ID: | 199905210552.BAA20540@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >Again very clear, and caused by the indexing of regex's, as you suggest.
> >I can easily look for '|' in the string, and skip the optimization. Is
> >that the only special case I need to add?
>
> What about '{' ?
Does it understand {? Man, what kind of regex library do we have?
--
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 | 1999-05-21 05:53:39 | Re: [HACKERS] Broken select on regular expression !!! |
| Previous Message | Don Baccus | 1999-05-21 05:13:15 | Re: [HACKERS] Broken select on regular expression !!! |