strange behavior with phpmyadmin and innodb tables

Hello,

I recently converted all my existing MyISAM tables to InnoDB tables
through phpmyadmin. I noticed some strange behavior whenever I would
refresh the screen, as phpmyadmin would report different numbers for the
cardinality of the primary key (i.e. one minute it would say cardinality
388, then 244 on refresh, then something else), and it would report
different values for the number of rows when mousing over the table
names on the left menubar. This behavior only seems to exist on tables
with a "larger" number of rows, and by larger I only mean ~100 or more
rows (tables with fewer rows always report the correct number of rows).

Whenever I do a SELECT *, I get the correct number of rows returned, so
I know they are actually there.

Has anyone ever experienced this or does anyone know what is up? Thanks.

Marcus,
> Has anyone ever experienced this or does anyone know what is up? Thanks.

I have a database with 45,000 rows. This seems to happen to me all the
time with that one. It seems odd because sometimes with the cardinality
being different the number of rows returned in the select are
different quite a bit of the time.

Mike

Marcus (JumpMan222@aol.com) decided we needed to hear...
> Hello,
>
> I recently converted all my existing MyISAM tables to InnoDB tables
> through phpmyadmin. I noticed some strange behavior whenever I would
> refresh the screen, as phpmyadmin would report different numbers for the
> cardinality of the primary key (i.e. one minute it would say cardinality
> 388, then 244 on refresh, then something else), and it would report
> different values for the number of rows when mousing over the table
> names on the left menubar. This behavior only seems to exist on tables
> with a "larger" number of rows, and by larger I only mean ~100 or more
> rows (tables with fewer rows always report the correct number of rows).
>
> Whenever I do a SELECT *, I get the correct number of rows returned, so
> I know they are actually there.
>
> Has anyone ever experienced this or does anyone know what is up? Thanks.
>
This happens because row count is only an estimate for InnoDB tables
due to the storage format. For MyISAM on the other hand, MySQL
maintains an exact row count.
--
Dave <dave@REMOVEbundook.com>
(Remove REMOVE for email address)