#33135: Read-only parameter for model fields
-------------------------------------+-------------------------------------
Reporter: mkalioby | Owner: nobody
Type: New | Status: new
feature |
Component: Database | Version:
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
New DBMS provides virtual columns that are generated based on another
column value in the row, these fields are read-only from DBMS prospective,
so they shouldn’t be included in insert or update statements.
My suggestion is to add **read-only** flag to the BaseField class and if
the flag is true, it shall be skipped from insert/update and can be
selected as usual.
I can do it, if the community will accept it.
--
Ticket URL: <https://code.djangoproject.com/ticket/33135>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.527453bc0bbd5adb3da041c2540a6fb1%40djangoproject.com.
