Re: Google Summer of Code Updates - Class based indexes

- Add support for column ordering (ASC/DESC) in class based indexes Completed - tests, docs, code PR - https://github.com/django/django/pull/6982 - Implement Hash index class Add capability to get type of index in introspection (required for testing this feature)

Re: Need help with MySQL 5.7 crashing on Django's Jenkins

hi. please post your /etc/my.ini (or your equiv. mysql ini config file). 2016-08-01 21:05 GMT-03:00 Tim Graham : > Sometimes the MySQL 5.7.13 builds on Ubuntu 16.04 are failing with "Lost > connection to MySQL server during query" because the MySQL server restarts > during

Re: [ANNOUNCE] Django 1.10 and 1.9.9 released

Awesome! Thanks Tim, once again, for driving the release process on time. Love your work! On Tuesday, 2 August 2016 05:03:27 UTC+10, Tim Graham wrote: > > Django 1.10 and a bug fix release for the 1.9 series (1.9.9) are now > available: > >

Need help with MySQL 5.7 crashing on Django's Jenkins

Sometimes the MySQL 5.7.13 builds on Ubuntu 16.04 are failing with "Lost connection to MySQL server during query" because the MySQL server restarts during the tests. I wonder if anyone has an idea about how to solve this. Looking through the MySQL error log, I think this is the root cause:

Re: Extend support for long surnames in Django Auth

Dear all, I kind of agree with Aymeric, increasing last_name to max=60 characters would already be good enough for this proposal and should cover 99.99% of users without breaking backward compatibility. I support your idea of a built-in User model not based on first and last name. But that

Re: Extend support for long surnames in Django Auth

Hello James, > On 01 Aug 2016, at 15:03, James Pic wrote: > > Aymeric, it doesn't matter if tens of milions of names fit into your > model, it only takes one to have a issue that's going to require the > project developers to invest time in it. I’m not an adept of the

Re: Extend support for long surnames in Django Auth

I agree with Aymeric. Short of actual stats stating otherwise, I think we should use max_length=60 and accommodate most people on the planet out of the box without a non-trivial amount of time/effort. For those who want to go above an beyond for a handful of potential users, they can create a

Re: Extend support for long surnames in Django Auth

> On 30 Jul 2016, at 23:15, Donald Stufft wrote: > > See #6 of > https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ I’m aware of this article. It's a entertaining read but, unlike the W3 Q mentioned earlier, it doesn’t contain actionable advice