-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sqlcmd profile improvements #459
Comments
I think we should diagnose first why we have some many nans, and then decide what's the best way to replace them. For example, if the table doesn't have the STDEV function, perhaps we can show another string or change the color - this is the only case where the behavior should differ from pandas. For the other cases, we should look at how pandas handles it. |
hey @yafimvo: did you start working on this? I can assign it to somebody else |
@edublancas No |
cool. I'll assign it to someone else. |
On it! |
So the table profiling is a bit unclear on how to read the output and what to do with nan values.
For instance, running on the table below, it could be
nan
for many reasons, wrong datatypes, db doesn't support the unique functions (STDEV function), confusing values (2.456e+01
) etc.We should improve the guide and the functionality of it, and produce a result that's similar in essence to the pandas profiling report.
@edublancas feel free to add more context.
The text was updated successfully, but these errors were encountered: