Karsten Hilbert <[EMAIL PROTECTED]> writes:
>> Regexes are optimized the same way as equivalent LIKE expressions. In
>> particular, the pattern has to be left-anchored to consider using it
>> with an index. In LIKE that means no wildcard at the start of the
>> pattern, in regex it means there has
> Regexes are optimized the same way as equivalent LIKE expressions. In
> particular, the pattern has to be left-anchored to consider using it
> with an index. In LIKE that means no wildcard at the start of the
> pattern, in regex it means there has to be a ^.
What about "^.*oobar" in a regex ? I
"Nick Barr" <[EMAIL PROTECTED]> writes:
>> Isn't there also a performance benefit as you can use an index if you
>> say "this definitely starts at the beginning" with the '^'?
> That is what I was thinking, which is the other reason why I put it in.
> This is only the case with the default locale
> [mailto:[EMAIL PROTECTED] Behalf Of Együd Csaba
> > Sent: Wednesday, January 14, 2004 6:43 AM
> > To: [EMAIL PROTECTED] (E-mail)
> > Subject: [GENERAL] Using regular expressions in LIKE
> >
> >
> > Hi All,
> > I'd like to "compress" the
Gulf Homes / Ashton Woods Homes
[EMAIL PROTECTED]
Fax: (416) 441-9085
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Együd Csaba
> Sent: Wednesday, January 14, 2004 6:43 AM
> To: [EMAIL PROTECTED] (E-mail)
> Subject: [GENERAL] Using
Hi All,
I'd like to "compress" the following two filter expressions into one -
assuming that it makes sense regarding query execution performance.
... where (adate LIKE "2004.01.10 __:30" or adate LIKE "2004.01.10 __:15")
...
into something like this:
... where adate LIKE "2004.01.10 __:(30/15)"
