That sounds preferable to me instead of forcing everyone to use a subclass.
Any feedback from MSSQL users? If we were to do this, then all Columns specified as type Unicode() would now be CREATE'd as NVARCHAR instead of VARCHAR. Note again that regular VARCHAR works for utf-8, so nothing is going away and there would be no new type requirement -- mostly the worry is about breaking existing code with Unicode() types. Is there any out there? Rick On 1/8/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
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" type and "String" would not be involved. all other dialects would return None when given "Unicode". >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
