Re: [sqlalchemy] MSSQL String columns often incorrectly encoded as NVARCHAR

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 continue passing str/unicode

Re: [sqlalchemy] MSSQL String columns often incorrectly encoded as NVARCHAR

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 continue passing str/unicode for Unicode > columns. I'm on the mailing list looking for help with why my solution > doesn't work

Re: [sqlalchemy] MSSQL String columns often incorrectly encoded as NVARCHAR

Thanks for the reply, Mike! the NVARCHAR thing should not happen if you are comparing to a > non-NVARCHAR column. it only occurs when there is no other context > that SQLAlchemy can determine the correct datatype for the Unicode > object being passed. This was my impression as well. I am,