MySQL Bugs: #9451: Selecting rows with null primary key does not always return the empty set

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:	None
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

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Output of SHOW VARIABLES in the test environment

Attachment: MySQLVars.txt (text/plain), 17.67 KiB.

SQL Script to reproduce the behaviour

Attachment: MySQLScript.txt (text/plain), 1.47 KiB.