Bug #6330 Corrupt output with innodb tables using mysql client
Submitted: 29 Oct 2004 17:45 Modified: 1 Nov 2004 15:15
Reporter: Tim Bishop Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:4.1.7 OS:Solaris (Solaris 9)
Assigned to: CPU Architecture:Any

[29 Oct 2004 17:45] Tim Bishop
Description:
The difference is subtle - there is two spaces before the * in the second example. I'm using MySQL 4.1.7 on Solaris 9 (compiled myself to fit into our structure). This came about from using RT (www.bestpractical.com) but the problem shown here is from the mysql command line client.

I'm not sure if this could be a corrupt database... but it seems unlikely given the first examples works correctly.

mysql> SELECT * FROM Queues WHERE Name = 'cs-syshelp'\G
*************************** 1. row ***************************
               id: 3
             Name: cs-syshelp
      Description: CS Systems Support
CorrespondAddress: cs-syshelp@kent.ac.uk
   CommentAddress: cs-syshelp-comment@kent.ac.uk
  InitialPriority: 0
    FinalPriority: 99
     DefaultDueIn: 0
          Creator: 12
          Created: 2003-07-14 14:45:30
    LastUpdatedBy: 12
      LastUpdated: 2003-07-17 11:05:54
         Disabled: 0
1 row in set (0.00 sec)

mysql> SELECT  * FROM Queues WHERE Name = 'cs-syshelp'\G
*************************** 1. row ***************************
 B: 3
 @: cs-syshelp
   : CS Systems Support
   : cs-syshelp@kent.ac.uk
   : cs-syshelp-comment@kent.ac.uk
  : 0
  : 99
  : 0
  : 12
  : 2003-07-14 14:45:30
  : 12
  : 2003-07-17 11:05:54
        @: 0
1 row in set (0.01 sec)

mysql> 

How to repeat:
I haven't attempted to repeat this.
[30 Oct 2004 8:31] Heikki Tuuri
Hi!

This is probably a general mysqld/mysql bug, not InnoDB-related.

Heikki
[31 Oct 2004 7:53] Heikki Tuuri
Tim,

I am not able to repeat this on Linux with a test table of mine.

Can you test with a mysql client from the standard MySQL distro?

Regards,

Heikki

mysql> select * from alex1 where symbole = 'aA1164'\G
*************************** 1. row ***************************
   tiny1: 28
   tiny2: 28
  small1: 812
 symbole: aA1164
symbole2: bb
symbole3: c75268
symbole4: d4068t
symbole5: e82084f
symbole6: g96428
symbole7: h812
    date: 2001-04-03 12:54:00
   first: 7.31000
    high: 7.31000
     low: 7.31000
    last: 7.31000
  volume: 200
1 row in set (0.00 sec)

mysql> select  * from alex1 where symbole = 'aA1164'\G
*************************** 1. row ***************************
   tiny1: 28
   tiny2: 28
  small1: 812
 symbole: aA1164
symbole2: bb
symbole3: c75268
symbole4: d4068t
symbole5: e82084f
symbole6: g96428
symbole7: h812
    date: 2001-04-03 12:54:00
   first: 7.31000
    high: 7.31000
     low: 7.31000
    last: 7.31000
  volume: 200
1 row in set (0.00 sec)
[31 Oct 2004 10:01] Tim Bishop
I'm afraid I'm currently unable to do any further testing. I needed the system available asap so I removed the offending mysql from our cluster and replaced it with something that worked for now. I am able to get it back... but it'll take a bit of time to restore it into our development environment for testing... I guess I can try and do that this coming week.

Sorry - I appreciate this isn't very helpful.
[1 Nov 2004 12:01] Tim Bishop
Sorry - I am unable to replicate this again. This isn't a problem for me any more (I've moved the database to another system), so feel free to just ignore it if you want.
[1 Nov 2004 15:15] Heikki Tuuri
Hi!

I am setting this to the 'Can't repeat' status. Let us wait if some other user encounters this strange problem.

Regards,

Heikki