Here's a question for those of you experienced integrating MSSQL and web2py.
My web2py apps connect to a legacy SQL Server 2005 database, but I'm
running into a problem where any attempts to *insert *unicode data into my
nvarchar fields breaks the encoding (Renée -> Renée)
It seems the Unicode query strings get to SQL Server, but are then assumed
to be ASCII (there's no leading N before the string literals), and get
encoded.
Switching the DAL to use MSSQL2 fixes the problem, as it converts *all* queries
to ASCII:
def execute(self,a):
return self.log_execute(a.decode('utf8'))
But I understand MSSQL2 is experimental, possibly deprecated, and many of
you must be managing to work with Unicode data just fine using the
MSSQL/3/4 adapters.
This issue occurs in both a linux stack (Web2py > pypyodbc > freetds 8.0 >
MSSQL2005) and web2py running on a local windows machine (web2py > pyodbc >
Windows ODBC? > MSSQL2005)
Any thoughts? Has anyone else run into this?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
