I've revised the documentation section for clarity about external hosting,
and given the lack of further discussion or dissention, I'm now taking the
DEP to the technical board for a decision.
Andrew
On Sun, Jun 12, 2016 at 4:35 AM, Andrew Godwin
wrote:
>
> On 12 Jun 2016 2:00 a.m., "Tim Graham
Hi, I would like to get some help pointing out where is the ideal place to
do these transformations for doing lookups on DateTimeRangeField using
__contains=`datetime`.
I got a basic working solution at
https://github.com/django/django/compare/master...ar45:support_dt_range_contains
I would great
Hi everyone,
I have raised few days ago an issue (
https://code.djangoproject.com/ticket/26822) I encountered when using
--keepdb and --parallel option.
I have proposed a patch (https://github.com/django/django/pull/6884), and
after some exchanged with Aymeric Augustin, I have been encouraged to p
- Restructure index migrations
PR - https://github.com/django/django/pull/6866
Modified the internal working of migrations/schema methods related to
indexes. This mainly aims at stabilising the newly added migrations for
Index class.
- Introduce Meta.indexes
PR ready
Hello,
> On 5 juli 2016, at 00:22, Romain Garrigues
> wrote:
> After some investigation, I have seen that, in case of keepdb context, in
> django/db/backends/*/creation.py, if the cloned databases already exist, we
> don't touch them, which leads to this new field not created in cloned ones.
>