Opened 3 months ago
Closed 3 months ago
#36406 closed New feature (wontfix)
Add a unique identifer as an attribute for each model field that can be overriden by the developer
Reported by: | BMI | Owned by: | |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 5.1 |
Severity: | Normal | Keywords: | Unique Identifier of the fields |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Apps of Django have models that have classes that have fields.
If Django has a a feature that builds a map of the projects. Hence to provide a unque universal key identifier of the fields (like f'{App}{ModelName}{FieldName}') then it can allow having automated queries that can be comparable to graphene and graphql .. by which the server can create views on the fly either by searching field name of the fields or by providing their unique ID by the requests.
Allowing the user to enter key ID of choice in the fields will prevent exposing the internal server architecture to the clients and users.
All it takes is only to generate the fields ID either automatically or by the user. to reference them in the requests. the permission can be assessed class based
it is possible to write such feature without amending the source code of Django but it will be more complex. Because it require tracking the fields in django and provide them with ID's.
Change History (1)
comment:1 by , 3 months ago
Component: | Uncategorized → Database layer (models, ORM) |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Summary: | Creating a Unique Key Identifier fo the Field that can be overriden by the developer → Add a unique identifer as an attribute for each model field that can be overriden by the developer |
It's redundant to open a Trac ticket. and a django/new-features issue. I'll close this and we could reopen it if there's consensus for the feature.