Bug #4477 MA reports PRIMARY KEY indexes as allowing NULL values
Submitted: 8 Jul 2004 23:21 Modified: 13 Jul 2004 2:52
Reporter: Harrison Fisk Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.6-beta OS:Linux (Debian Linux)
Assigned to: Alfredo Kojima CPU Architecture:Any

[8 Jul 2004 23:21] Harrison Fisk
When viewing the catalogs information section, if you go to the indexes tab, then it will list PRIMARY KEYs as Null Allowed = Yes.  Indexes that do allow NULLs for real will have nothing in that category.  Basically it looks like it is reversed.  This same bug was reported in earlier versions of the Windows MA as BUG#2851, but wasn't present in the Linux version at the time.

How to repeat:
1.  Run MA.
2.  Go to Catalogs option.
3.  Click on Indexes tab at top.
4.  Select a database.
5.  Notice all of the primary keys say they allow nulls.

Suggested fix:
Fix whatever was done with the Windows MA to make it work.
[13 Jul 2004 2:52] Alfredo Kojima
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 bugfix, yourself. More information 
about accessing the source trees is available at