Thanks. I’ll pursue those avenues.
Cheers,
Ian
2019년 4월 1일 (월) 11:30, Mike Bayer 님이 작성:
> On Sun, Mar 31, 2019 at 10:12 PM Ian Wagner
> wrote:
> >
> >
> > My suggestion would be a pymssql dialect-level patch to send bytestrings
> for String columns, and of course c
but we'd have to develop an all new behavior
> > for 1.4 if we are to start encoding these binds again, however current
> > behavior has been this way for many years and this is the first it's
> > being reported in this way. I would want to look into driver
> >
Hello all,
I'm trying to get to the bottom of an issue in which Python 3 (unicode by
definition) strings are always encoded as NVARCHAR for at least two
backends (pymssql and pyodbc). Using bytstrings as comparison arguments
(for example Table.column == value.encode('utf-8')) sends a regular st
