Paul Johnston wrote:
3) unicode fields
Ticket #298 had been created for this, but is not a complete solution. I
have re-opened the ticker, with this comment:
Unicode columns are still created as VARCHAR. The problem is that
Unicode is a TypeDecorator
like i said in the ticket, all TypeDecorator types define what type
they are wrapping using the impl class member. dialect-specific
Unicode types which want to subclass Unicode need only define a
different impl member so that they wrap whatever String subclass you
want.
another thing we might do if you want Unicode to act database-neutral
is add a step at line 85 of types.py to ask the dialect first for a
type_descriptor of Unicode, then if not found to ask for the impl
version which is normally String. The MSSQL dialect would return
NVARCHAR for the Unicode
Hi,
return adodbapi.connect('Provider=SQLOLEDB;Data Source=.;User
Id=pythonweb;Password=mdi*2mdO1;Initial Catalog=test')
Ooops! I thought I had just managed to cancel that mail in time :-)
Paul
--~--~-~--~~~---~--~~
You received this message because you
