Yeah sorry, I should have caught that. On the pymssql vs. adodbapi, the answer is not an easy question, and is quite a mixed bag.
MS supports ADO (at least for now), and no longer supports DB-Lib, so from that standpoint adodbapi would be the way to go, at least as regards the toolchain from the DB-API to the SQL server. On the other hand, I have heard that the adodbapi project has been unresponsive as of late. Pymssql seems to be pretty reliable once set up correctly, but of course relies on the now-unsupported DB-lib, and has the aforementioned issues with partial result reads. All told, I would use adodbapi on Windows, and pymssql on *nix. I have my eye on the pyodbc project, that might end up being the "one best way" for MS-SQL connections, and would open up other ODBC compliant data sources as well. Course that won't help you in the near-term.... Rick On 2/8/07, Arnar Birgisson <[EMAIL PROTECTED]> wrote: > > On 2/8/07, Rick Morrison <[EMAIL PROTECTED]> wrote: > > > > If you're using FreeTDS, I assume you're on some kind of Unix. As far > > as I know, adodbapi is Windows-only (anyway, it has its own set of > > idiosyncrasies too). > > Yes, Linux. I mentioned that in the first post so I deducted from your > question that I had a choice :o) > > Anyways, freetds has always been a pain in my ... neck, I've moved a > few projects over to windows servers. > > Let's say that I do that, should I use pymssql or adodbapi? > > Arnar > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
