Hi All,
I'm keen to avoid being bitten by annoying unicode decoding and encoding
errors, particularly later during project development (you know, when
the stuff that no longer fits into the encoding you accidentally used
turns up once you think development is done and dusted ;-) )
What's the best way to do this? Avoid Text and String columns and use
Unicode and UnicodeText columns everywhere?
Assuming that is the case, what about where you're reflecting a
database's tables rather than defining them and those tables do have
encoded columns?
I see the convert_unicode option to sqlalchemy.types.String and, more
likely to get used by me, the convert_unicode option to create_engine.
However, I'm wary of the convert_unicode behaviour warning that it will
"significant performance overhead". When does this happen and how do I
avoid it?
cheers,
Chris
PS: What happens with Text and String columns in Python 3?
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
