On Nov 29, 2011, at 11:18 PM, Dirk Makowski wrote:
> I see. Thanks for the explanation. I totally forgot to read the dialect
> specific docs... ;)
>
> Maybe it would be nice to have the general docs point out that specialities
> for a certain subject like encodings are also handled by some dia
Ah, there already is such a paragraph at create_engine(). Please ignore my
suggestion :)
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/sqlalchemy/-/VUPx-eF5CkMJ.
To post
P.S. for completeness:
As you had suggested,
create_engine(encoding='utf-8', convert_unicode=False,
client_encoding='utf8')
runs perfectly without "use_native_unicode".
-- Dirk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To view this discuss
I see. Thanks for the explanation. I totally forgot to read the dialect
specific docs... ;)
Maybe it would be nice to have the general docs point out
that specialities for a certain subject like encodings are also handled by
some dialects. E.g. for create_engine(): "Some dialects may have addit
On Nov 29, 2011, at 10:39 PM, Dirk Makowski wrote:
> Thanks for the quick reply. Passing use_native_unicode=False to
> create_engine() indeed prevents this error. Is this parameter missing in the
> docs for create_engine()
> (http://www.sqlalchemy.org/docs/core/engines.html#engine-creation-ap
Thanks for the quick reply. Passing use_native_unicode=False to
create_engine() indeed prevents this error. Is this parameter missing in
the docs for create_engine()
(http://www.sqlalchemy.org/docs/core/engines.html#engine-creation-api)?
I had assumed the "encoding" parameter to set the wanted
