Hi Tim,
Thanks for sharing your experience!
> On 13 sept. 2015, at 01:48, Tim Allen <flip...@peregrinesalon.com> wrote:
> We have a test suite performing table creates / destroys, basic CRUD
> operations, stored procedure execution, and more against both pyodbc and
> pymssql.
> pymssql outperforms pyodbc significantly against SQL Server, especially on
> SELECT and INSERT operations.
Did you mean “pyodbc outperforms pymssql”? Or did you go with pyodbc despite
lower performance? (Or did I misread that?)
> pymssql on Linux offers no stable Django options, as noted throughout this
> thread.
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.
> pyodbc offers several options.
> we initially started using django-pyodbc (lionheart on GitHub), which worked
> but required quite a few tweaks to the settings.
> we moved to django-pyodbc-azure, which we found a much easier install /
> Django DATABASES {} configuration, and is kept up to date in a timely fashion.
>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.
--
Aymeric.
--
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/A38482C5-64CF-4E3F-B86C-E60956678B6C%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.
