#13867: Feature request: docstring and comments in Django models saved to
database
schema
---------------------------------------------------+------------------------
Reporter: rjalves | Owner: nobody
Status: new | Milestone: 1.3
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by rjalves):
For PostgreSQL yes, for MySQL something like:
{{{
CREATE TABLE `bacteria`.`dummy` (
`dummy_name` VARCHAR ( 20 ) NOT NULL COMMENT 'All dummies should have
names right?'
) ENGINE = InnoDB COMMENT = 'This comment goes into the schema.'
}}}
I agree with the point about the docstring magic, however for the column
comment I think they should be kept separate.[[BR]]
One may want to include a content specific comment in the database and a
different message in help_text as user guideline.
--
Ticket URL: <http://code.djangoproject.com/ticket/13867#comment:2>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
