[sqlalchemy] Re: MSSQL & Time - Christophe de VIENNE - com.googlegroups.sqlalchemy

19 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: MSSQL & Time

From	Sent On	Attachments
Christophe de VIENNE	24 Jul 2007 03:22
Paul Johnston	24 Jul 2007 03:50
Christophe de VIENNE	24 Jul 2007 04:33
Christophe de VIENNE	24 Jul 2007 05:29
Paul Johnston	24 Jul 2007 05:34
Christophe de VIENNE	24 Jul 2007 05:46
Christophe de VIENNE	24 Jul 2007 08:36
Rick Morrison	24 Jul 2007 12:03
sdob...@sistechnology.com	24 Jul 2007 13:27
Rick Morrison	24 Jul 2007 13:29
sdob...@sistechnology.com	24 Jul 2007 14:05
Paul Johnston	26 Jul 2007 10:06
Paul Johnston	26 Jul 2007 10:07
Paul Johnston	26 Jul 2007 10:10
Rick Morrison	26 Jul 2007 10:13
Christophe de VIENNE	26 Jul 2007 10:21
sdob...@sistechnology.com	26 Jul 2007 10:38
Rick Morrison	26 Jul 2007 10:51
Rick Morrison	26 Jul 2007 11:24

Subject:	[sqlalchemy] Re: MSSQL & Time
From:	Christophe de VIENNE (cdev...@gmail.com)
Date:	07/26/2007 10:21:54 AM
List:	com.googlegroups.sqlalchemy

2007/7/26, Paul Johnston <pa...@pajhome.org.uk>:

One thing PyMSSQL will never support is Unicode - the MSSQL interface is uses is deprecated and just doesn't do unicode. For that reason, you may do better to focus your efforts on getting PyODBC working better on Unix. Right at the minute though it's more problematic than PyMSSQL.

I could see that... One thing though : - pymssql, on unix, is based on freetds - pyODBC, at least on my system, use an ODBC driver based on freetds The question is : if pymssql does not support unicode, does it mean that freetds doesn't ? Sub-Question : if FreeTDS supports unicode, is it realistic to try and modify pymssql to make it more specific to freetds and support unicode ?

Christophe