If anyone is interested in listening in on the meetings with Microsoft engineers (Wednesday and Thursday 9am-5pm Pacific), let me know and I'll send you the Skype link.
On Friday, October 2, 2015 at 11:53:17 AM UTC-7, Meet Bhagdev wrote: > > > > On Thursday, October 1, 2015 at 12:32:25 PM UTC-7, Tim Graham wrote: >> >> Hi Meet, >> >> I was wondering.... >> >> 1. If you have any progress updates since your last message? >> > > > * Yes, engineers on my team I are currently ramping up on the three > Django-SQL Server adapters* > > > - * Django-pymssql* > - * Django-pyodbc-azure* > - > * Django-mssql * > > * The goal is to have a thorough understanding of what’s good and > what’s bad with these adapters before the event. * > >> >> 2. If you have any further details on the schedule for the time in >> Seattle in a week and a half? (including video conference details for those >> unable to attend in person) >> > > - *We will have a video conference link for Day 2 and Day 3. > Participants interested can join the conference stream from their browser. > The conference room mics are only capable to a certain extent. Thus the > quality might be a little poor. * > > > - *We are finalizing the detailed schedule this week and will post it > on this thread by next Friday. * > > > 3. If myself or the other attendees should do anything to prepare for the >> meetings? >> >> *Here are some things that you should prepare before coming to > Seattle.* > > *- * > > > - > * Have a clear understanding of the things that you need from > Microsoft to improve the SQL Server support on Django. We have resources > to > do the heavy lifting but need guidance. * > - * Share with us the issues we can help fix (on the Django side > and on the Django-ORM(database) side). * > > > Thanks! >> >> On Thursday, September 17, 2015 at 3:38:09 PM UTC-4, Tim Allen wrote: >>> >>> Hey team, as promised, here are the simple tests I put together to >>> benchmark pyodbc vs pymssql. Be kind, this was Python I wrote a long time >>> ago! >>> >>> https://github.com/FlipperPA/pyodbc-pymssql-tests >>> >>> I've included example output on the README. Very basic, but useful. >>> >>> On Wednesday, September 16, 2015 at 11:27:59 AM UTC-4, Tim Allen wrote: >>>> >>>> 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/592840c9-c7d4-45d3-9c59-15a6a027899e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
