Opened 2 years ago
Closed 2 years ago
#34275 closed New feature (wontfix)
Add new Field named FieldAlias
| Reported by: | Sharif Mehedi | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 4.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Let's say I define some abstract model and when some database model inharits from the abstract model, I would like to have some other name for a field from the inharited model. This is fairly simple for most of the field types, with some changes in the query_utils. But This will need some extra work on GenericForeignKey, where I would like to have some FieldAlias which should behave like a ForeignKey (some inverse relation to a GenericRelation (which are not necessarily tied together)) on the GenericForeignKey.
Note:
See TracTickets
for help on using tickets.
Thanks for this ticket, it's an interesting idea but it's also quite niche. Personally, I would create a field subclass for frequently used set of field arguments.
It sounds like a third-party package is the best way to proceed so that people can try it out and then approaching the DevelopersMailingList to reach a wider audience and see what other think. Thanks.