Bug #2998 | Wrong values for index: Unique and not null | ||
---|---|---|---|
Submitted: | 27 Feb 2004 13:05 | Modified: | 11 Mar 2004 7:19 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.01a Alfa | OS: | Windows (XP Pro) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[27 Feb 2004 13:05]
[ name withheld ]
[27 Feb 2004 13:13]
[ name withheld ]
Sorry, null values is allowed both in primary key ( where it should not) and in the other indexes (where it is all right, when the index is no unique)
[1 Mar 2004 4:04]
Ulrich Bayer
Yes the unique column always displays the opposite of what is true. Moreover I would only like to see the values Yes/No there instead of UNIQUE and nothing. The Null colum seems to okay, but I had only tables with not-null keys to test.
[11 Mar 2004 7:19]
Michael G. Zinner
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 http://www.mysql.com/doc/en/Installing_source_tree.html