You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2024. It is now read-only.
When selecting a non datetime column as the date column, we get an empty dataframe error instead of an error explaining that the datetime column is not parsable.
The text was updated successfully, but these errors were encountered:
So if we accidentally select a double/float/int column as the datetime column, pandas can infer it as unix timestamp (which may be incorrect) and technically passes our datetime columm check. But after that it leads to a SQL error.
How do we want to deal with these type of columns?
Describe the bug
When selecting a non datetime column as the date column, we get an empty dataframe error instead of an error explaining that the datetime column is not parsable.
The text was updated successfully, but these errors were encountered: