Bug #95490 | Select distinct returns actual distinct values and NULL. But No NULL Value | ||
---|---|---|---|
Submitted: | 23 May 2019 10:53 | Modified: | 1 Jul 2019 12:51 |
Reporter: | Ragesh Kandathil | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
Version: | 5.7.26 | OS: | Red Hat |
Assigned to: | CPU Architecture: | Any |
[23 May 2019 10:53]
Ragesh Kandathil
[23 May 2019 14:01]
MySQL Verification Team
Hi, Thank you for your bug report. However, in order to process this bug, we need the entire test case. That includes, your configuration, table structure, all rows and the exact command. Without all of these, we can not process this report.
[28 May 2019 12:56]
MySQL Verification Team
Hi, Thank you for the info that you have supplied, but we do have some additional requests. First of all, please send us the output from SHOW CREATE TABLE ..... do not use DESCRIBE ..... Second, please include your query in that text file as well. Third, are you sure that only those two rows that you have sent us are satisfying conditions in the WHERE clause ??? Please be absolutely certain about that .... Last , but not least, all columns involved in the query are not only NULLable, but have NULL as a default value. Hence, simply put, we would need all data to reproduce the issue .....
[29 Jun 2019 1: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".