Hi guys, I'm in meetings all day today, but I've been watching a bit from the sidelines.
It's certainly fair to say that the ADODB interface to MSSQL is not super-well tested. We use pymssql here and that's what gets the most attention. Patches are absolutely and enthusiastically welcomed, especially those that include working tests and that adapt the test suite to better the test coverage for the MSSQL module. IIRC, there is already a patch in Trac for the NVARCHAR, but UTF-8 works fine in regular VARCHAR (at least via pymssql) . I believe that NVARCHAR is UTF-2 only, and unless you do some cross-encoding, it may not be what you expect. The self.HASIDENT should be set automatically from the table schema. My tests use it with explicit Table() constructors that use the psuedo-Sequence() mechanism for defining them, and it works fine -- are you using reflected tables? Rick On 1/2/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
patch away....MS-SQL is not necessarily super well-tested at this point. >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
