#18468: Add the ability to define comments in table / columns
-------------------------------------+-------------------------------------
Reporter: Marc Rechté | Owner: Jared
| Chung
Type: New feature | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jared Chung):
Status update: KimSoungRyoul has created a new PR
([https://github.com/django/django/pull/14463/ here]) that addresses some
of the suggestions raised by atombrella in May 2020 on the previous PR
([https://github.com/django/django/pull/12605 here]). Huge thanks to
KimSoungRyoul for resuming work on this feature!
The new PR is not complete yet. Still needed:
1) Test coverage.
2) Additional changes to the proposed docs including further explanation,
a warning about lack of SQLite support, and a warning about overwriting
comments made by DBAs in the db, versionadded annotation, and a couple
other things.
3) Release note.
4) General code review, especially related to where sqlite warnings should
be triggered in the code to avoid having hard-coded vendor names in
django/db/models/base.py.
Next steps: I'll add some suggestions directly to the new PR and post
updates here as this PR progresses.
--
Ticket URL: <https://code.djangoproject.com/ticket/18468#comment:32>
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/065.a49a2d434ef979374edfd0690e18914f%40djangoproject.com.
