Skip to content
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

yyyy-mm-dd formatted strings converted to epoch milliseconds #5301

Open
dobesv opened this issue Dec 4, 2020 · 0 comments
Open

yyyy-mm-dd formatted strings converted to epoch milliseconds #5301

dobesv opened this issue Dec 4, 2020 · 0 comments

Comments

@dobesv
Copy link

dobesv commented Dec 4, 2020

When a query result contains a string that "looks" like a "yyyy-mm-dd" date it is converted into an epoch millisecond. This could be any string field, regardless of its intended purpose.

If a column contains a mixture of values formatted in this way and values that are NOT formatted in this way, the values in this format are converted to epoch milliseconds and the values that are not in this format are not converted.

In this case choosing to format the column as a date to kind of "undo" the transformation is not sufficient.

Redash should not do this kind of arbitrary transformation on string data values unless it is explicitly requested by the user.

A similar issue was reported in #5237 but never fixed, as the user was able to work around it because that column was actually supposed to be a date.

However, I discovered this issue in a scenario where the field in question was mostly not intended to be a date, and having a large number stuck in there for some fields and not others was very confusing, to say the least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant