Bug #9451 | Selecting rows with null primary key does not always return the empty set | ||
---|---|---|---|
Submitted: | 29 Mar 2005 12:58 | Modified: | 29 Mar 2005 19:47 |
Reporter: | David Clements | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 4.1.10-nt-log | OS: | Windows (Windows XP) |
Assigned to: | Sergey Petrunya | CPU Architecture: | Any |
[29 Mar 2005 12:58]
David Clements
[29 Mar 2005 13:00]
David Clements
Output of SHOW VARIABLES in the test environment
Attachment: MySQLVars.txt (text/plain), 17.67 KiB.
[29 Mar 2005 13:01]
David Clements
SQL Script to reproduce the behaviour
Attachment: MySQLScript.txt (text/plain), 1.47 KiB.
[29 Mar 2005 19:47]
Sergei Golubchik
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: See http://dev.mysql.com/doc/mysql/en/create-table.html In particular, note: To make MySQL compatible with some ODBC applications, you can find the AUTO_INCREMENT value for the last inserted row with the following query: SELECT * FROM tbl_name WHERE auto_col IS NULL
[30 Mar 2005 2:57]
David Clements
Thank you for the quick and helpful response. My apologies for missing the documentation describing the special behaviour of IS NULL on auto_increment columns. I did actually try to follow your instructions for submitting a bug report, but I guess we all make mistakes. Next time I'll be more cautious and go through the forums first.