I think it would be acceptable to make related name clashes a check Error.
I'm guessing you couldn't find any justification for why the check doesn't
currently do this?
On Sun, 6 Sep 2020 at 11:31, Shai Berger wrote:
> Hi all,
>
> When you define a related field on a model -- a ForeignKey etc
Hi all,
When you define a related field on a model -- a ForeignKey etc -- it
usually adds its related-name as a backwards-accessor on the related
model. These related names are checked for clashes against other fields
and other related-names. But they are not checked for clashes against
other
When Django's mail subsystem generates an email, it creates a unique
Message-ID. This is a requirement specified in RFC2822 https://tools.ietf.org/html/rfc2822#section-3.6.4>.
The domain part of that Message-ID is generated by the Python network
utilities. It defacto is the domain name
On Sun, 6 Sep 2020 12:01:34 +0100
Adam Johnson wrote:
> I think it would be acceptable to make related name clashes a check
> Error. I'm guessing you couldn't find any justification for why the
> check doesn't currently do this?
>
I didn't find any, though I didn't look too hard.
On the other
Hi, I think https://code.djangoproject.com/ticket/6989 has some discussion
related to this.
On Sunday, September 6, 2020 at 7:30:15 AM UTC-4 jacob...@gmail.com wrote:
> When Django's mail subsystem generates an email, it creates a unique
> Message-ID. This is a requirement specified in
