[web2py] Re: Codec MS-SQL, unicode Latin1 UTF8

2017-05-25 Thread tim . nyborg
I use this same stack, and ran into encoding issues when updating the database, because of FreeTDS v.91. But upgrading to FreeTDS v1.00.40 fixed all unicode issues: https://github.com/mkleehammer/pyodbc/issues/244 Connect with mssql4n, TDS_Version 7.1+, no need to set db_codec On Friday, 19 May

[web2py] Re: Codec MS-SQL, unicode Latin1 UTF8

2017-05-23 Thread Tomasz Wrona
HI, I am using mssql4 adapter. For table: CREATE TABLE myTable ( Column_a varchar (10) COLLATE French_CI_AS NOT NULL, Column_b varchar (10) COLLATE Latin1_General_CI_AS NOT NULL, Column_c varchar (10) COLLATE Estonian_CS_AS NOT NULL) I create a view: CREATE VIEW v_myTable AS SELECT CONVERT (nv

[web2py] Re: Codec MS-SQL, unicode Latin1 UTF8

2017-05-19 Thread J-Michel Angers
Hello, Many thanks at both of you :-) I've just made a lot of tests, a lot of combinations I confirm : mssql4 is NOT the good connector for this. mssql2 works much better ! ! For unicode fields (type nvarchar in SQL-Server), mssql2 without codec works very well, but doen't work for varchar f

[web2py] Re: Codec MS-SQL, unicode Latin1 UTF8

2017-05-18 Thread Jose
Hi J-Michel Angers Given: pydal <-> pyodbc <-> UnixODBC <-> FreeTDS <-> MSSQL In freetds.conf I have: client charset = UTF-8 and in pydal I use mssql2 adapter, db_codec is not necessary Jose -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web

[web2py] Re: Codec MS-SQL, unicode Latin1 UTF8

2017-05-18 Thread Skiros
Hello J-Michel Angers I had have that problem and I dont remember how i fixed... jajaja what type of fields you are using ? nchar o char ? this determines what kind of connection need to use. There are a few options; mssql, mssql2, mssql3 and mssql4. If you are using nchar you need mssql2. In