Hi Owais,
I did not have the time to start any work on this. I'm very much interested
in this and I'd be happy to contribute to this in any way. I'm following
along on the other thread you started [1].
[1]
Like it has been discussed a while ago [1] about adding *db_default*, we
should stick with something similar to that and support updates as well.
My 2 cents here.
I like the idea Anssi has proposed to delegate as much as possible using
expressions. So I would propose similar to what discussed in
On Sunday 07 February 2016 19:47:48 Alex Poleha wrote:
> I apply my condition to default managers indeed and I see no problem here.
> Default manager is just first manager defined on class(or on it's non
> concrete base). It has no additional magic.
>
Well, I was using wrong terminology, sorry;
So, I've been working on https://code.djangoproject.com/ticket/25197
I have it as part of my own project, with a view to contributing to core
once it's polished.
Currently it has basic functionality - a JS widget that fires on load,
hides the textarea, and produces a table of (name, value,
Reading your description again, it seems like you apply the condition to
default managers as well. Default managers are not "specific to the class they
are defined on", and I see no problem in their inheritance. In particular:
class BaseComment(models.Model):
... some
Great work!
On Saturday, February 6, 2016 at 4:27:42 PM UTC+1, Tim Graham wrote:
>
> Triaged
>
> ---
>
> https://code.djangoproject.com/ticket/26162 - Data loss when
> ManyToManyField refers to the wrong table (accepted)
>
> https://code.djangoproject.com/ticket/26168 - BooleanField is
There are many places that expressions can extend to, and I think indexes
would make a really good candidate. There are a few things that need to
happen to make this work though.
- create meta.indexes to store { index_name: IndexType('field') }
- internally translate any db_index=True to the
