There are a lot of twiddly little issues with the MSSQL SA module, yeah. They are primarily necessary because of the dual-headed nature of the beast, trying to support adodbapi and pymssql at the same time.
Both interface modules have small issues with -- type conversion (date vs datetime, unicode vs string) -- the Windows-specific incantations necessary to marry the Windows COM object model with Python in adodbapi (things like your CoInitialize() ) -- the differing cursor models supported by pymssql (simple "fire-hose" cursors), and adodbapi (choice of client side or server-side cursors) and other issues seen in the past: -- MSSQL's behavior when attempting to throw away partially read query results in a server-side cursor when issuing a new query -- The oddball mechanism of getting new IDENTITY rows via a separate query instead of a cursor variable -- The even odder mechanism needed to insert literal non-null IDENTIFY values -- The MSSQL INFORMATION_SCHEMA views don't seem to know what IDENTITY columns are, making table reflection messy and you've got yourself a twiddle-fest, yep. Twiddler assistants welcome! - Rick On 1/1/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
hi Paul - If you want to make a patch for these changes, that would be great. Im looking at mssql.py and it seems to have a lot of twiddly details for both pymssql and ado (I didnt write the mssql.py module), so I can't readily say what the proper solutions should be. Rick Morrison is the maintainer of the mssql.py module, so if you can illustrate the specific lines for your changes we can get Rick's input on them. - mike >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
