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

UnicodeEncodeError on migrate #243

Closed
sqlalchemy-bot opened this issue Nov 16, 2014 · 6 comments
Closed

UnicodeEncodeError on migrate #243

sqlalchemy-bot opened this issue Nov 16, 2014 · 6 comments
Labels

Comments

@sqlalchemy-bot
Copy link

@sqlalchemy-bot sqlalchemy-bot commented Nov 16, 2014

Migrated issue, originally created by Vasily Asakasinsky (@asakasinsky)

# an error occurs here:

# default.arg = '\u0411\u0435\u0437 \u043d\u0430\u0437\u0432\u0430\u043d\u0438\u044f'  
# default.arg is the TextClause instance
 default = str(default.arg.compile(
                dialect=autogen_context['dialect']))

Attachments: tracelog.txt

@sqlalchemy-bot
Copy link
Author

@sqlalchemy-bot sqlalchemy-bot commented Nov 16, 2014

Changes by Vasily Asakasinsky (@asakasinsky):

  • edited description
1 similar comment
@sqlalchemy-bot
Copy link
Author

@sqlalchemy-bot sqlalchemy-bot commented Nov 16, 2014

Changes by Vasily Asakasinsky (@asakasinsky):

  • edited description
@sqlalchemy-bot
Copy link
Author

@sqlalchemy-bot sqlalchemy-bot commented Nov 17, 2014

Michael Bayer (@zzzeek) wrote:

  • Fixed a variety of issues surrounding rendering of Python code that
    contains unicode literals. The first is that the "quoted_name" construct
    that SQLAlchemy uses to represent table and column names as well
    as schema names does not repr() correctly on Py2K when the value
    contains unicode characters; therefore an explicit stringification is
    added to these. Additionally, SQL expressions such as server defaults
    were not being generated in a unicode-safe fashion leading to decode
    errors if server defaults contained non-ascii characters.
    fixes #243

a02719d

@sqlalchemy-bot
Copy link
Author

@sqlalchemy-bot sqlalchemy-bot commented Nov 17, 2014

Changes by Michael Bayer (@zzzeek):

  • changed status to closed
@sqlalchemy-bot
Copy link
Author

@sqlalchemy-bot sqlalchemy-bot commented Nov 17, 2014

Michael Bayer (@zzzeek) wrote:

i dont think I got every potential unicode problem but that changeset should fix the one you have and a bunch of others.

@sqlalchemy-bot
Copy link
Author

@sqlalchemy-bot sqlalchemy-bot commented Nov 17, 2014

Vasily Asakasinsky (@asakasinsky) wrote:

Thank you, Mike!

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

Successfully merging a pull request may close this issue.

None yet
1 participant