This repository was archived by the owner on Aug 7, 2018. It is now read-only.
New database options: collation and client_encoding #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since I'm not able to configure FreeTDS/ODBC client to use utf-8,
everything is encoded in latin-1. Thus, the decode('utf-8') throws
UnicodeDecodeError when it comes to non-ascii characters.
Client_encoding option allows me to specify the input encoding.
Iv
pushed a commit
to Iv/django-pyodbc
that referenced
this pull request
Jun 28, 2013
Iv
pushed a commit
to Iv/django-pyodbc
that referenced
this pull request
Jun 28, 2013
onysos
pushed a commit
to onysos/django-pyodbc
that referenced
this pull request
Apr 15, 2014
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there,
I'm sending fixed commits.
First, I've fixed the collation option, since it was using the old-style DATABASE_OPTIONS settings.
Second, I had a problem with UTF-8. I got UnicodeDecodeError that some string can't be decoded to UTF-8. I wasn't able to configure FreeTDS/ODBC to use utf, so I rather added another option — client_encoding. Setting this option to 'latin-1' fixed my problem. I tried to look for simpler solution, but haven't found anything.