IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

IWETHEY Home / IWETHEY Board / Databases Forum / No idea, just a wild guess
Post #160,524
by Meerkat
6/19/04 11:44:39 AM
Reply
New No idea, just a wild guess
Do subsequent inserts take even longer? Maybe it's doing a full table scan for some reason - but even then that shouldn't take 40 seconds. But the only thing I know about MySQL is how to spell it (and I may even have the capitalisation all wrong) so who knows.

Does it have Oracle-esque 'Explain Plan' functionality that may give a clue?
Two out of three people wonder where the other one is.
Post #160,529
by drewk
Picture of drewk
6/19/04 1:59:38 PM
Reply
New Full table scan is faster
I already tested doing a search on the (non-indexed) blob column the data is in. (Remember there are fewer than 40 rows so far.) Even that search takes less time than the insert, so it's not a scan.
===

Implicitly condoning stupidity since 2001.
     Why would a database insert take >40 seconds? - (drewk) - (7) - June 19, 2004, 03:14:14 AM EDT
         No idea, just a wild guess - (Meerkat) - (1) - June 19, 2004, 11:44:39 AM EDT
             Full table scan is faster - (drewk) - June 19, 2004, 01:59:38 PM EDT
         Are there indexes on other columns? - (ben_tilly) - (4) - June 19, 2004, 03:39:54 PM EDT
             Here's the table - (drewk) - (3) - June 21, 2004, 10:10:54 AM EDT
                 What are the indexes though? -NT - (admin) - (2) - June 21, 2004, 10:20:35 AM EDT
                     Called KEY in mysql - (drewk) - (1) - June 21, 2004, 10:41:58 AM EDT
                         Oh, heh. Never mind. - (admin) - June 21, 2004, 11:00:21 AM EDT

The rest of the nutzo stuff du jour.
63 ms