-
Notifications
You must be signed in to change notification settings - Fork 138
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
Odo Function with encoding error: ValueError: Unsupported string encoding u'SQL_Latin1_General_CP1_CI_AS' #426
Comments
Hi, |
Having the same issue here with a SQL Server db - |
+1 With this same error. The code that breaks is on datashape\coretype.py, looking for the collation on the following dictionary:
Since SqlServer doesn't support UTF I can't see what I can set the collation to to make it work... |
Are there any updates on this? We're still having an issue with this and we would like to use odo but this is prohibiting us from using it. It would be fantastic if this were prioritized and resolved. Any chances that can happen? |
See also blaze/datashape#176 |
For me, the fix in #430 fixed this. |
Good to close? |
I've been running a locally patched version but thought I'd try to update to the latest to see if this is fixed. It appears that #430 does fix this issue so I'm happy that this can be closed now that's merged. I'll just note that there's no release yet which incorporates the fix in #430 so I had to keep running odo from source to verify. |
df = odo(url_source+"::NibrasEBSElementMap", pd.DataFrame, encoding='cp1512')
and
df = odo(url_source+"::NibrasEBSElementMap", pd.DataFrame, encoding='latin1')
results in following error
The text was updated successfully, but these errors were encountered: