Re: getting in trouble with multiple insert...

[Brent Baisley]

I assume you have your ORDER BY field indexed, but your query may not 
permit the index to be used for sorting. If you are selecting most of 
the data set or very large portions of it, you may try using HAVING 
instead of WHERE for you filter. Then the index can be used for the 
sort. MySQL will be forced to scan the whole table, but if you are 
grabbing most of the table anyway, it doesn't matter.
You just want to make sure you have fast disks.

On Thursday, July 10, 2003, at 10:25 AM, Michael Schoen wrote:

BUT with the multiple insert statment the chronological order will be
lost and IŽll need the ORDER BY syntax again. And the query-speed goes
down to not usable ;(
--
Brent Baisley
Systems Architect
Landover Associates, Inc.
Search & Advisory Services for Advanced Technology Environments
p: 212.759.6400/800.759.0577
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]