mysql_insert_id returns the correct value to my application when I insert a
single
row using the INSERT...VALUES syntax. However, when I insert multiple rows,
it always returns 0. This is inconsistent with the behavior of
LAST_INSERT_ID,
which returns the id of the first row.
Has anyone else
- Original Message -
From: Jeremy Zawodny [EMAIL PROTECTED]
On Wed, May 30, 2001 at 11:32:16PM -0400, Michael Villalba wrote:
I have a rather large MyISAM table (~230 million rows) running under
MySQL 3.23.30. It has 10 columns and 3 indices. The data and index
files each
(same model). All the
drives were delivered with the unit.
The E450 has 4 400MHz processors installed. It has one additional
Symbios controller.
- Original Message -
From: Steve Brazill [EMAIL PROTECTED]
To: Michael Villalba [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, May
I have a rather large MyISAM table (~230 million rows) running
under MySQL 3.23.30. It has 10 columns and 3 indices. The data
and index files each occupy about 10GB.
My problem is that sorting the rows using myisamchk --sort-records
takes an extremely long time. The last sort took 95 hours
I have a rather large table (~130 million rows) running under MySQL
3.23.30 and have been very pleased with the performance of the
database. However, occasionally I have to delete millions of rows
from the table, and it appears that MySQL hangs on these jobs. To
be specific, I am running a