The build status is Failed to build, but I fairly sure that an update
to 5.1.54 would fix this issue.
--
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
The build status is Failed to build, but I fairly sure that an update
to 5.1.54 would fix this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706988
Title:
Major Bug in MySQL 5.1.49 up to
I'm not 100% sure. I've found the faulty behavior with 2 keys on both
DEFAULT NULL columns.
This bug has (had) a lot of different effects and is fixed (as already
mentioned) in 5.1.53
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I'm not 100% sure. I've found the faulty behavior with 2 keys on both
DEFAULT NULL columns.
This bug has (had) a lot of different effects and is fixed (as already
mentioned) in 5.1.53
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
