strange behavior with phpmyadmin and innodb tables

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Marcus
    #1

    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.
    Tags: None
    • Mike Willbanks
      #2
      Re: strange behavior with phpmyadmin and innodb tables

      Marcus,[color=blue]
      > Has anyone ever experienced this or does anyone know what is up? Thanks.[/color]

      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

        Comment

        • Dave
          #3
          Re: strange behavior with phpmyadmin and innodb tables

          Marcus (JumpMan222@aol .com) decided we needed to hear...[color=blue]
          > 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.
          >[/color]
          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@REMOVEbun dook.com>
          (Remove REMOVE for email address)

            Comment

            Previous template Next
            Working...