Bug #10227 | empty select | ||
---|---|---|---|
Submitted: | 28 Apr 2005 7:15 | Modified: | 7 May 2005 7:22 |
Reporter: | Jan Benda | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S1 (Critical) |
Version: | 5.0.4 | OS: | Linux (Fedora3,Windows98) |
Assigned to: | Timour Katchaounov | CPU Architecture: | Any |
[28 Apr 2005 7:15]
Jan Benda
[28 Apr 2005 7:32]
Hartmut Holzgraefe
also happens with current bk build
[7 May 2005 7:22]
Timour Katchaounov
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 Additional info: I could reproduce the bug on an a several days old tree, but it can't be reproduced in the latest BK tree. Therefore I assume that the bug has been already fixed by some current push. Some info just in case: I localized the problem down to the insertion of rows with default values. In this case if there are more than 7 columns, the remaining columns got NULLs stored instead of the default value for the column.