> > There can be another source of problems with REPLACE. As it has to
> > DELETE a row first, it might take a lot of time on huge table if MySQL
> > is not able for some reason to utilize index in order to locate rows.
>
> Now this seems like it might be related. On a variable sized row
> table, this could be a source of problems. As a note, there is a
> unique index it should be using. Is there a way to see if it is,
> or USE INDEX like select?
Some clarification. On this table there are a lot of indexes, but there is
one unique/primary key, and it is that one that the replace should be
checking for. The other indexes have the same fields in different places
though. Table key def is something like this:
PRIMARY KEY (f,m),
KEY (f,d,a),
KEY (f,d,p,m),
KEY (u,d,a,f),
KEY (i,d,a,f),
KEY (l,d,a,f),
FULLTEXT (t,m),
FULLTEXT (a,e),
KEY (f,r,d,m)
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
