Opened 3 years ago

Last modified 2 years ago

#17814 new New feature

RELATED_NAME_OVERRIDES

Reported by: yanchenko.igor@… Owned by: nobody
Component: Database layer (models, ORM) Version:
Severity: Normal Keywords:
Cc: slav0nic0@… Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: yes Patch needs improvement: yes
Easy pickings: no UI/UX: no

Description

I use external apps with same name models (for example it's forum.post and blog.post) and have conflict with related_name, both have

user = models.ForeignKey(User, related_name="posts")

I writed patch with principle like ABSOLUTE_URL_OVERRIDES

Attachments (1)

concept.patch (1.9 KB) - added by yanchenko.igor@… 3 years ago.

Download all attachments as: .zip

Change History (4)

Changed 3 years ago by yanchenko.igor@…

comment:1 Changed 3 years ago by carljm

  • Needs documentation set
  • Needs tests set
  • Patch needs improvement set
  • Triage Stage changed from Unreviewed to Accepted

I really hate the use of a setting for this (despite the precedent of ABSOLUTE_URL_OVERRIDES, which I don't like either). I do think it's a problem that Django should provide some answer for, so accepting the ticket on that basis. I can't immediately think of a better solution than the setting, but I hope we can think of one.

comment:2 Changed 3 years ago by anonymous

possible settings are not the best place for this, but this is the most obvious place, if I meet the discrepancy with the code model, I would like to find it in the settings, but not in another application.

comment:3 Changed 2 years ago by slav0nic

  • Cc slav0nic0@… added
Note: See TracTickets for help on using tickets.
Back to Top