Bug #31635 Varsize primary key(s) are broken in 5.0
Submitted: 16 Oct 2007 13:45 Modified: 15 Dec 2007 8:56
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0, 5.0-wl2325-5.0 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[16 Oct 2007 13:45] Jonas Oreland
Description:
.

How to repeat:
.

Suggested fix:
.
[16 Oct 2007 14:27] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/35655

ChangeSet@1.2165, 2007-10-16 16:25:15+02:00, jonas@perch.ndb.mysql.com +6 -0
  ndb - bug#31635 (drop6)
    0 pad varsize primary key(s) as mysqld does not (5.0 only)
[26 Oct 2007 6:42] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/36402

ChangeSet@1.2475, 2007-10-26 08:42:33+02:00, jonas@perch.ndb.mysql.com +4 -0
  ndb - bug#31635 (5.0)
    0 pad varsize keys in ndbapi
[14 Nov 2007 12:12] Jonas Oreland
pushed to 50-ndb
[14 Nov 2007 12:14] Jonas Oreland
and this only affect 5.0
[14 Dec 2007 17:08] Bugs System
Pushed into 5.1.23-rc
[14 Dec 2007 17:09] Bugs System
Pushed into 5.0.56
[14 Dec 2007 17:09] Bugs System
Pushed into 6.0.5-alpha
[15 Dec 2007 8:56] Jon Stephens
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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented in 5.0.56 changelog only, per developer comments, as:

        Primary keys on variable-length columns (such as
        VARCHAR) did not work correctly.