MySQL Bugs: #6135: SELECT * FROM <table> returns byte count error

Bug #6135	SELECT * FROM <table> returns byte count error
Submitted:	17 Oct 2004 15:45	Modified:	25 Oct 2004 11:40
Reporter:	Timothy Parez	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S1 (Critical)
Version:	1.0 Beta 1	OS:	Windows (XP Pro)
Assigned to:	Reggie Burnett	CPU Architecture:	Any

Description:
Hi,

I can run a DESCRIBE TABLE on my table:

KlantNummer	int(11)		PRI	(null)	auto_increment
Username	varchar(50)		UNI	(null)	
Password	varchar(100)			(null)	
Naam	varchar(100)			(null)	
Voornaam	varchar(100)			(null)	
Straat	varchar(100)			(null)	
StraatNr	varchar(10)			(null)	
Gemeente	varchar(100)			(null)	
Postcode	varchar(10)			(null)	
DefaultMail	varchar(255)	YES	MUL	(null)	
BtwNr	varchar(50)	YES		(null)	
ReceiveMail	tinyint(1)			(null)	
Online	tinyint(1)			(null)	
LastVisit	timestamp(14)	YES		(null)	
Categorie	int(11)			(null)	

However when I do a SELECT * FROM KLANT I get
"Unexpected byte count received
SELECT * FROM KLANT"

I have tried deleting this table and recreating it, no effect
With the ByteFX 0.76 I did not have this problem

SHOW TABLE STATUS returns the same problem
"Unexpected byte count received
SHOW TABLE STATUS"

SHOW TABLES works just fine

More info:
MySQL Server Version: v3.23.58

How to repeat:
I've no idea.

Please note that I tried at different stages

1) the table with data in it
2) the table after it had been truncated
3) the table after it had been dropped and recreated

Can you post the output of a SHOW CREATE TABLE for this bug?

CREATE TABLE `KLANT` (
  `KlantNummer` int(11) NOT NULL auto_increment,
  `Username` varchar(50) NOT NULL default '',
  `Password` varchar(100) NOT NULL default '',
  `Naam` varchar(100) NOT NULL default '',
  `Voornaam` varchar(100) NOT NULL default '',
  `Straat` varchar(100) NOT NULL default '',
  `StraatNr` varchar(10) NOT NULL default '',
  `Gemeente` varchar(100) NOT NULL default '',
  `Postcode` varchar(10) NOT NULL default '',
  `DefaultMail` varchar(255) default '',
  `BtwNr` varchar(50) default '',
  `ReceiveMail` tinyint(1) NOT NULL default '0',
  `Online` tinyint(1) NOT NULL default '0',
  `LastVisit` timestamp(14) NOT NULL,
  `Categorie` int(11) NOT NULL default '0',
  PRIMARY KEY  (`KlantNummer`),
  UNIQUE KEY `UniqueUsername` (`Username`),
  UNIQUE KEY `UniqueDefaultMail` (`DefaultMail`)
) TYPE=MyISAM

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Additional info:

I can't repeat  using this NUnit test case.

		[Test()]
		public void Bug6135() 
		{
			string sql = "CREATE TABLE `KLANT` (`KlantNummer` int(11) NOT NULL auto_increment, " +
				"`Username` varchar(50) NOT NULL default '', `Password` varchar(100) NOT NULL default '', " + 
				"`Naam` varchar(100) NOT NULL default '', `Voornaam` varchar(100) NOT NULL default '', " +
				"`Straat` varchar(100) NOT NULL default '', `StraatNr` varchar(10) NOT NULL default '', " +
				"`Gemeente` varchar(100) NOT NULL default '', `Postcode` varchar(10) NOT NULL default '', " +
				"`DefaultMail` varchar(255) default '', 	`BtwNr` varchar(50) default '', " + 
				"`ReceiveMail` tinyint(1) NOT NULL default '0',	`Online` tinyint(1) NOT NULL default '0', " +
				"`LastVisit` timestamp(14) NOT NULL, `Categorie` int(11) NOT NULL default '0', " +
				"PRIMARY KEY  (`KlantNummer`),	UNIQUE KEY `UniqueUsername` (`Username`), " +
				"UNIQUE KEY `UniqueDefaultMail` (`DefaultMail`)	) TYPE=MyISAM";
			execSQL( sql );

			MySqlCommand cmd = new MySqlCommand("SELECT * FROM KLANT", conn);
			MySqlDataReader reader = null;
			try 
			{
				reader = cmd.ExecuteReader();
				while (reader.Read()) { }
			}
			catch (Exception ex) 
			{
				Assert.Fail( ex.Message );
			}
			finally 
			{
				if (reader != null) reader.Close();
			}
	  }

I think it might be specific to this version of MySQL
and it would seem that after the administrators restarted the server
it worked just fine.

Sorry about the confusion, but at this time I can't replicate the exception anymore

Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem is not the result of a bug.
For a list of more appropriate places to ask for help using MySQL
products, please visit http://www.mysql.com/support/

Thank you for your interest in MySQL.