Michael Bayer wrote:
On Oct 8, 2008, at 8:54 PM, jason kirtland wrote:
Most likely you just need to configure the db-api's client encoding by
adding ?charset=utf8 onto your connection URL.
Enough folks have hit this recently that I'm (again) considering
passing
through the engine
Michael Bayer wrote:
On Oct 9, 2008, at 3:39 AM, jason kirtland wrote:
i don't know about your env, but the unit tests under mysql use
testing.engines.utf8_engine to configure a connection that can send
unicode across the wire without encoding failures.
I can run python
Thanks all! The connection string is getting unicode into the db
intact.
Is it possible that the charset is set in my.conf or elsewhere on some
environments?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
On Oct 9, 2008, at 3:39 AM, jason kirtland wrote:
i don't know about your env, but the unit tests under mysql use
testing.engines.utf8_engine to configure a connection that can send
unicode across the wire without encoding failures.
I can run python test/sql/testtypes.py --db mysql
On Oct 9, 2008, at 10:02 AM, Michael Bayer wrote:
On Oct 9, 2008, at 3:39 AM, jason kirtland wrote:
i don't know about your env, but the unit tests under mysql use
testing.engines.utf8_engine to configure a connection that can send
unicode across the wire without encoding failures.
I
I had similar problems, part of it turned out to be the encoding send
from the browser.
on forms you can set the encoding (in the formtag, check
http://www.w3schools.com
if the page is other than UTF-8 (check your browser view-
encoding menu).
I changed everything to utf-8 by setting
joelanman wrote:
Hi,
Firstly - I'm hugely impressed with SQLAlchemy - it's really helped me
a lot with my new project.
I'm having problems storing international characters in mysql using
SQLAlchemy. For example:
école—school
looks like this in mysql:
école—school
I'm
On Oct 8, 2008, at 8:54 PM, jason kirtland wrote:
Most likely you just need to configure the db-api's client encoding by
adding ?charset=utf8 onto your connection URL.
Enough folks have hit this recently that I'm (again) considering
passing
through the engine encoding= parameter to the
