On Thursday, 27. June 2002 21:26, [EMAIL PROTECTED] wrote:
Hi,
> I apologize for not being more specific. The query that is taking too long
> is :
> SELECT * FROM Stories WHERE UCASE(Path) LIKE 'toUpper(path)%';
> Path is a 255 char field with an index on it. path is variable passed in.
> Thanks
L PROTECTED]
> Subject: Hardware Planning
>
>
> I am currently using mysql 4.01 with caching for web page serving. I
> pull several records out with a like statement on a text field. The db
> consists of about 200,000 records right now and it is using 100%
> of the cpu
>
"Benjamin Pflugmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, June 27, 2002 3:08 PM
Subject: Re: Hardware Planning
> Hi.
>
> On Thu 2002-06-27 at 13:35:28 -0400, [EMAIL PROTECTED] wrote:
> > I am currently using mys
Hi.
On Thu 2002-06-27 at 13:35:28 -0400, [EMAIL PROTECTED] wrote:
> I am currently using mysql 4.01 with caching for web page serving. I
> pull several records out with a like statement on a text field. The db
> consists of about 200,000 records right now and it is using 100% of the cpu
> whe
At 12:35 PM 6/27/2002, you wrote:
> I am currently using mysql 4.01 with caching for web page serving. I
>pull several records out with a like statement on a text field. The db
>consists of about 200,000 records right now and it is using 100% of the cpu
>when the search is ran.
> Since thi
I am currently using mysql 4.01 with caching for web page serving. I
pull several records out with a like statement on a text field. The db
consists of about 200,000 records right now and it is using 100% of the cpu
when the search is ran.
Since this is a critical function, it is ran on al
