Bug #7336 NULL values inconsistent upon export
Submitted: 15 Dec 2004 21:30 Modified: 16 Jan 2005 20:52
Reporter: Steve Chupack Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.2 OS:Microsoft Windows (Win XP)
Assigned to: CPU Architecture:Any

[15 Dec 2004 21:30] Steve Chupack
Description:
When exporting a result set (in any format), NULL values are sometimes exported as (null), sometimes as ""

This happens to me when performing left joins where null values are returned for rows that do not exist. I did a brief test with a single table containing null values and I could not replicate the issue -- but I didn't try that hard.

Bottom line is this: The query browser reports null values, but does not always export null values.

My apologies in advance if I'm somehow misunderstanding how column definitions and left joins affect what is returned. But one would think the Query Browser and Export should give identical values.

Thanks for continuing to develop the product!

How to repeat:
Perform a left join that returns null values for non-existent rows in the righthand table. Query Browser should correctly show all columns in unmatched rows as null. Then export the result set to any format -- you should some of the nulls appear as (null), some as "".
[16 Dec 2004 20:33] MySQL Verification Team
Hi,

Thank you for the report.
Could you test it with version 1.1.3? I wasn't able reproduce it with MySQL Query Browser 1.1.3
[16 Dec 2004 20:52] Steve Chupack
The behavior is still there in 1.1.3, only a little different. I think the best thing for me to do is provide you with the tables and queries that I'm using. Might be a week... Thanks for your time!
[14 Feb 2005 22:54] 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".