Bug #7694 MySQL Admin showing incorrect data
Submitted: 5 Jan 2005 21:50 Modified: 30 May 2005 9:43
Reporter: Craig Stadler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.18 OS:Windows (Windows2000 Server)
Assigned to: Michael G. Zinner CPU Architecture:Any

[5 Jan 2005 21:50] Craig Stadler
Description:
MySQL 4.0.23 Win32
MySQL Admin 1.0.18

1. Select Catalogs
2. Select Database
3. Delect Schema Tables tab
4. Incorrect Data length column, Incorrect Index length column may reflect a larger problem involving table corruption.

How to repeat:
1. Select Catalogs
2. Select Database
3. Delect Schema Tables tab
4. Incorrect Data length column, Incorrect Index length column

Screen print shown at 
http://64.2.11.29/screen.jpg

Database would have to be sent as a DVD for testing as it is 
dbZIP.MYD (2,137,558 kb)
dbZIP.MYI (2,577,500 kb)
dbZIP.frm (9 kb)

Table create (struct) as follows:

dbzip | CREATE TABLE `dbzip` (
  `Filespec` varchar(254) NOT NULL de
  `Name` varchar(254) NOT NULL defaul
  `Heading` int(11) NOT NULL default
  `Size` int(11) default NULL,
  `R` char(1) default NULL,
  `ClipInfo` varchar(254) default NUL
  `AudioVideo` char(1) default NULL,
  `ClipLength` int(11) default NULL,
  `Bandwidth` int(11) default NULL,
  `TS` timestamp(14) NOT NULL,
  `Contents` blob,
  `AltTag` varchar(254) default '',
  `NameSpaced` varchar(254) default '
  `namelink` varchar(254) default NUL
  `VidX` int(11) default NULL,
  `VidY` int(11) default NULL,
  PRIMARY KEY  (`Filespec`),
  UNIQUE KEY `IDX_R2` (`R`,`Filespec`
  KEY `IDX_R` (`Filespec`(15),`R`),
  KEY `IDX_TS` (`TS`)
) TYPE=MyISAM MAX_ROWS=100000000

Suggested fix:
Either a bug exists in 

1. MySQL 4.0.23
2. MySQL Admin 1.0.18
3. My table definition for the amount of data stored in this table.
[20 Jan 2005 1:44] Craig Stadler
What is the status of this ticket???
[30 May 2005 9:43] Michael G. Zinner
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html