Bug description
I am using Superset 4.1.3 for MySQL database, and I noticed that boolean fields are not displayed correctly in the Explore/SQL Lab table preview.
For example, fields like:
Enabled
EmailConfirmed
PhoneNumberConfirmed
TwoFactorEnabled
LockoutEnabled
Instead of showing true / false (or 1 / 0), Superset displays them as small icons (stacked lines), making it difficult to read and interpret boolean data.
Screenshots/recordings
Superset version
4.1.3
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
This is a known UI limitation in Superset 4.1.3: boolean fields are rendered as icons (specifically, the FieldBinaryOutlined icon) in Explore and SQL Lab, rather than as true/false or 1/0 text values. This behavior is controlled by the frontend rendering logic and type inference, and is especially common with MySQL, where boolean fields are often stored as TINYINT(1) and may be mis-inferred by Superset's type detection. There is currently no configuration option or setting to change this rendering to text in Superset 4.1.3; changing it would require frontend code changes. Multiple users have found this confusing and have requested more readable alternatives, but as of now, it is not configurable or fixed in this version reference.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: sadpandajoe
@dosubot is this fixed in other versions?
Comment From: dosubot[bot]
Yes, this is fixed in newer versions. The BooleanCell component in the Superset frontend now renders boolean values as text ("true" or "false") instead of icons, which addresses the issue you described in 4.1.3. This change is present in the current codebase as of 2025 see implementation.
There isn't a specific changelog or pull request directly mentioning this fix, but the code confirms the new behavior. If you upgrade to a recent release, boolean fields should display as readable text in Explore and SQL Lab.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
Comment From: sandy4597niko
@sadpandajoe i have upgraded 4.1.4 version but it did not work. can you tell me in which specific version it is fixed?
Comment From: sadpandajoe
@sandy4597niko ok, so just in the 4.1 versions but we haven't looked at 5.0?