-
Notifications
You must be signed in to change notification settings - Fork 50
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
Column type detection issues #241
Comments
@sagoyal2 it looks like this is the source of the problem:
We'll have to look into why this would be happening, it's doing a test on the column to determine the data type and perhaps seeing the column as an It only does this when it's trying to infer the data type, so as a workaround you can create your table first in OmniSci which will then read the types from the schema instead of trying to infer them. For reference, it's one (or more) of the |
Actually after looking at the code block it's debatable that it's a bug at all. If the type of the Pandas dataframe is We need to decide if this is "just the way it works" or if we do something more complicated with the auto detection, like check the types of the first 1000 rows instead, with additional rules for which data type wins when they are of different types. If we decide we should do something, perhaps the most logical alternative would be to keep the detection the same as the OmniSci detection itself - ie. using the same logic as the |
I tried to upload a pandas dataframe to Immerse however I got the following errors
Input:
The text was updated successfully, but these errors were encountered: