Hi Mysql,
E-Mail vom Montag, 3. September 2001, 12:14:42:
Hi Jeremy,
E-Mail vom Montag, 3. September 2001, 11:52:55:
>> My problem with the REPLACE is that the documentation says that a
>> REPLACE always does an DELETE and then an INSERT. In my case a lot
>> of rows (99%) would be deleted in the index that only need an
>> update. Is it a good idea to do that much index manipulations that
>> aren't necessary?
> Hmm. Are you asking for performance reasons or just because one is
> easier to code than the other?
I'm just afraid that the system get's damages Index-files when I do
that much unnecessary index-updates.
At the moment we get about one damaged file in 2 months (isamcheck).
But this replace operation will increase index-manipulation
dramatically.
> It shouldn't be hard to benchmark both options. I'd be curious to
> hear what you find.
Haven't done it yet ...
Ciao, Stephan
--
sql table
---------------------------------------------------------------------
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
