Hi.
Thanks for your response>
[EMAIL PROTECTED] wrote:
Do you have any idexes on the table?
No.
The table looks like this.
Would there be any advantage in creating indexes for it?
| id | | LastUpdated |
| 32957c615b37b5674f99d1cfd06d6a23 | | 20060416075614 |
| 33d1d3a8b63c983a67ec5ab38d148774 | | 20060416003803 |
| 3b0d2f1e5c2fe60377220aa146abd926 | | 20060411095312 |
| 3c61d917967fb3ed45fa2ed8efb67aa8 | | 20060413150746 |
| 4e0debc18ce34d8f131e05664f9df6da | | 20060411104352 |
What does your
mysql> show create table tbl_name \G
/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mysql> show create table sessions \G
*************************** 1. row ***************************
Table: sessions
Create Table: CREATE TABLE `sessions` (
`id` char(32) NOT NULL,
`a_session` longtext,
`LastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update
CURRENT_TIMESTAMP,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1
1 row in set (0.00 sec)
mysql>
\_________________________________________
Thanks.
Kind regards.
In theory, theory and practice are the same;
in practice they are not.
On Thu, 13 Apr 2006, Luke Vanderfluit wrote:
To: mysql@lists.mysql.com
From: Luke Vanderfluit <[EMAIL PROTECTED]>
Subject: innodb vs myisam
Hi.
I have the following myisam table:
The table is only 32,000 rows, but over 60Megs in size. And mysql seems
to be wanting to write to that file alot, so it may well be trying to
seek all over the disk looking for the right spot all the time.
Does innodb do a better job at keeping the file on the disk smaller?
Does an innodb table take up less disk space than myisam?
Is an innodb table compacter and would therefore require less disk seek
time or I/O than myisam?
Kind regards.
Luke.
--
Luke
