On Aug 29, 2008, at 10:53 AM, Mike wrote:
If I use pymssql instead, it works. As I understand it, SA should be
using pymssql anyway, so I don't know why this is happening. I can
cast the unicode to a string, so it's not a big deal. However, I
thought someone might want to know that this is
Hi Mr. Bayer,
On Aug 29, 10:10 am, Michael Bayer [EMAIL PROTECTED] wrote:
On Aug 29, 2008, at 10:53 AM, Mike wrote:
If I use pymssql instead, it works. As I understand it, SA should be
using pymssql anyway, so I don't know why this is happening. I can
cast the unicode to a string, so
and then I do the following where someValue happens to be a unicode
string:
pref.pref_value = someValue
session.commit()
That's not going to work with pymssql as your DBAPI. Pymssql is based on
Microsoft's DBLib (circa 1991 or so), which does not support unicode and
never will: it's been
Hi Rick,
On Aug 29, 11:02 am, Rick Morrison [EMAIL PROTECTED] wrote:
and then I do the following where someValue happens to be a unicode
string:
pref.pref_value = someValue
session.commit()
That's not going to work with pymssql as your DBAPI. Pymssql is based on
Microsoft's DBLib
