[Bug 706988] [NEW] Major Bug in MySQL 5.1.49 up to 5.1.52

[Christian Koller]

Public bug reported:

There is a major bug in MySQL 5.1.49 up to 5.1.52 currently delivered
with Ubuntu 10.10

Example:

DROP TABLE IF EXISTS `foo`;
CREATE TABLE IF NOT EXISTS `foo` (
  `a` int(11) DEFAULT NULL,
  `b` int(11) DEFAULT NULL,
  KEY `foo_a` (`a`),
  KEY `foo_b` (`b`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

INSERT INTO `foo` (`a`, `b`) VALUES
(1, 1),
(1, 2),
(1, 2),
(1, 2),
(1, 3),
(2, 1);

SELECT a FROM foo where a=1 and b=2;   results in 0 rows returned.
The only way to avoid this, would be to remove one of the keys, or make the columns not null.

Such a faulty version should not be deployed.
It is fixed in 5.1.53 and up.

Tested on:
Ubuntu 10.10
5.1.49-1ubuntu8.1

** Affects: mysql-5.1 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: faulty mysql result select wrong

** Tags added: mysql

** Tags added: faulty result select wrong

** Description changed:

  There is a major bug in MySQL 5.1.49 up to 5.1.52 currently delivered
  with Ubuntu 10.10
  
  Example:
  
  DROP TABLE IF EXISTS `foo`;
  CREATE TABLE IF NOT EXISTS `foo` (
-   `a` int(11) DEFAULT NULL,
-   `b` int(11) DEFAULT NULL,
-   KEY `foo_a` (`a`),
-   KEY `foo_b` (`b`)
+   `a` int(11) DEFAULT NULL,
+   `b` int(11) DEFAULT NULL,
+   KEY `foo_a` (`a`),
+   KEY `foo_b` (`b`)
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
  
  INSERT INTO `foo` (`a`, `b`) VALUES
  (1, 1),
  (1, 2),
  (1, 2),
  (1, 2),
  (1, 3),
  (2, 1);
  
  SELECT a FROM foo where a=1 and b=2;   results in 0 rows returned.
  The only way to avoid this, would be to remove one of the keys, or make the columns not null.
  
- 
  Such a faulty version should not be deployed.
+ It is fixed in 5.1.53 and up.
  
  Tested on:
  Ubuntu 10.10
  5.1.49-1ubuntu8.1

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/706988

Title:
  Major Bug in MySQL 5.1.49 up to 5.1.52