Thanks for all of your efforts, Aymeric, I've been following your project since its inception - I'm FlipperPA on GitHub.
On Sunday, September 13, 2015 at 4:59:34 AM UTC-4, Aymeric Augustin wrote: > > Did you mean “pyodbc outperforms pymssql”? Or did you go with pyodbc > despite lower performance? (Or did I misread that?) > We went with pyodbc, despite lower performance. I've been meaning to put the simple tests up on GitHub - making a note to do that this week. At the time we were looking at options, we couldn't find a stable Django option for pymssql. I should have been more clear about the time frame in which we were testing as well; this was right around the time that you first started django-pymssql. > > - django-pymssql is basically django-mssql on Linux. We could debate > whether django-pyodbc-azure is more stable than django-mssql. There’ve > been > a bunch of forks over the years. > > > I’m not going to argue it further because I would inevitably sound like > I’m tooting my own horn which isn’t my intent. I will just say that the > picture isn’t all that clear. > There is definitely much more to consider now, than when we were first assessing options. I will say I've been impressed with django-pyodbc-azure staying up to date with Django's releases. >From the perspective of someone who works on Django’s internals, I believe > django-pyodbc-azure could use a review of how the Django database backend > API is implemented. > > For example, looking at the new transaction APIs I introduced in 1.6, I > see that it commits or rolls back implicitly in _set_autocommit. At best > that’s weird and useless, at worst a data corruption bug. > > Nothing that couldn’t be fixed, but just because the code works doesn’t > means it handles edge cases well. django-mssql probably fares a bit better > since its author cooperated with and eventually joined the core team. > > Thanks to the abstraction provided by the Python DB-API, it should be > quite easy to port code implementing Django’s database backend API between > django-mssql and django-pyodbc-azure anyway. > You certainly know this stuff more intimately that me, I can just relay my experience, and hope it helps! Either way, a driver provided from Microsoft that offers better performance, easier installation and configuration, and more features would be a win for us all. The amount of time I've seen people spend trying to get FreeTDS + unixODBC + pyodbc running is substantial. Thanks again for your efforts - they're very much appreciated, and I'll check out django-pymssql again soon, it has been over a year. Regards, Tim -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/91bba226-f8df-479c-8265-3d021d0cc383%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
