Hi Paul, Yes, I had found this about the datatype size by way of breaking into the relevant code and setting the parameter length manually. This made the query work but just unveiled other problems.
I too made no further efforts to get it work as pymssql works fine for my purposes - although server side cursors would have been nice to have. However, the adodbapi module is fairly simple, it's mostly just proxying to the underlying COM api. I'm pretty sure it's relatively easy to fix but since I don't have any real need for it myself I lack the motivation right now. Maybe someday if the DB-API becomes defunct due to microsoft dropping support for it.. It's good to hear that someone is working on pyodbc support in SA. Arnar On 2/17/07, Paul Johnston <[EMAIL PROTECTED]> wrote: > > Arnar, > > I agree that is an adodbapi problem; I have seen this as well. It is > because adodbapi isn't setting the length of the parameter, so ADO is > defaulting to 1 - hence you only getting "O". I do have an idea how to > fix this, however I'm choosing not to for now. adodbapi just isn't > maintained any more - the mailing list is all but dead, and numerous > attempts to contact the author have failed. Moreover, pyodbc is now a > very viable alternative. I had been avoid ODBC because earlier versions > had no Unicode support, but this is now fixed. So, from now I will be > devoting my energies to making SQLAlchemy work better with pyodbc. > > Paul > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
