Bug #26206 | Subselect having null value result noting | ||
---|---|---|---|
Submitted: | 9 Feb 2007 5:22 | Modified: | 12 May 2007 15:42 |
Reporter: | Cuaap | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.27 | OS: | Windows (Win server 2003) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Subselect having null value result nothing |
[9 Feb 2007 5:22]
Cuaap
[9 Feb 2007 7:47]
Max Fischer
That's how a subquery works. If it finds a null, it voids the result.
[9 Feb 2007 7:50]
Max Fischer
Respecting the second one, it is a bug. When you explicitly send a null value to a non-null column, it is expected to have an error. But if you left that column out of the field list in the insert statement, than it should fill with the default value.
[9 Feb 2007 10:57]
Sveta Smirnova
Thank you for the report. Please provide output of SELECT @@sql_mode;
[10 Mar 2007 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[12 Apr 2007 15:42]
Valeriy Kravchuk
Feedback is still needed.
[12 May 2007 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".