Good merge!
Should this also be a policy change, or is it better to maintain a position
of "if it's relatively easy and unobtrusive"?
On Sunday, 18 November 2018 10:08:43 UTC+11, Tim Graham wrote:
>
> Okay, I've merged the PR, https://github.com/django/django/pull/10654.
>
> On Saturday, Novembe
Week ending November 17, 2018
Triaged
---
https://code.djangoproject.com/ticket/29946 - Weird session behavior after
upgrading to Django 1.11.16 (needsinfo)
https://code.djangoproject.com/ticket/29947 - Inlines containing a field
with default value are considered empty and not saved (wo
Okay, I've merged the PR, https://github.com/django/django/pull/10654.
On Saturday, November 17, 2018 at 12:11:17 PM UTC-5, Markus Holtermann
wrote:
>
> Agreed, let's add official 3.7 support.
>
> /Markus
>
> On Sat, Nov 17, 2018, at 1:15 PM, Adam Johnson wrote:
> > Since it's about 3 lines in
Agreed, let's add official 3.7 support.
/Markus
On Sat, Nov 17, 2018, at 1:15 PM, Adam Johnson wrote:
> Since it's about 3 lines in django itself, I think it's a good idea to
> backport and save users the pain.
>
> On Fri, 16 Nov 2018 at 15:37, Ramiro Morales wrote:
>
> > On Fri, Nov 16, 2018
Although I admire the work that has gone into the package, I think it's
best kept separate.
As the creator of Django-MySQL I did once propose merging parts of it as
django.contrib.mysql, but I cooled to the idea when I realized it's easier
to make changes when not kept in lock-step with Django. Fo
Since it's about 3 lines in django itself, I think it's a good idea to
backport and save users the pain.
On Fri, 16 Nov 2018 at 15:37, Ramiro Morales wrote:
> On Fri, Nov 16, 2018 at 12:32 PM Tom Forbes wrote:
>
>> Do we have an idea of how many fixes would need to be backported?
>>
>
>
> https
Hi everyone,
In our company, we also use the ability to define our own indexes, but with
the current implementation of base Index class, we basically need to copy
several methods entirely from it.
What do we want is implement UNIQUE indexes with the UPPER function wrapper
around field names [1].
T
