--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscribe@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/484264c0-b7d1-4264-b8b5-8857847f6b53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHn91oesnBvY-mWXoHWa3sf8Vri%2B1qwRHat1yF%2B8Sdm0pU-LhQ%40mail.gmail.com.
I think we could implement that feature.(Yes I changed my mind from six years ago when I wontfix'd the ticket.)
--Aymeric.
On 8 Mar 2018, at 11:00, Jani Tiainen <red...@gmail.com> wrote:
Oracle supports comments as well.
7.3.2018 2.52 ip. "vanadium23" <cherno...@gmail.com> kirjoitti:
Hello, fellows.There was once a proposal about ability to add comments to table/columns in postgres: https://code.djangoproject.com/ticket/18468I re-read discussion in ticket, and it has ended with another proposal, that now migrations is within Django, so we can add this feature.I want to make it as a third-party libs, but has come to thought that need to extend SchemaEditor, but it's not good for maintainability.Also, not only postgres has this feature, but also MySQL.Motivation for this feature is that some sort of users can view code comments without access to VCS of the project.--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/484264c0-b7d1-4264-b8b5-8857847f6b53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9ff6c9f5-045e-4bc7-8331-060471b012e2%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a8bf7145-d878-4ef0-b39c-3ea3ad7f62ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
i will close this pullRequest caused by imperfection
https://github.com/django/django/pull/12605
I will bring a new PullRequest as soon as possible.
in at least a week
add parameter "db_column_comment" to Field()
and. db_table_comment
class AModel(models.Model): aaa = model.CharField(help_text="i am help_text", db_column_comment="i am db_comment",~~~) class Meta: db_table = "a_model_example_name" db_table_comment ="this is a_model comment ~~~~"
Hi felixxm
I want this feature to be reflected in Django.3.1
I know this feature that many people won't use.
but some people who communicate with DBA would be helpful this feature
sometimes ORM take control from DBA
like these situation...
DBAs: we want to know comment(help_text) not to *.py could you use COMMENT SQL in migrationFile?
Developers: No, It's Impossible because django ORM does not support COMMENT SQL
DBAs: ???? that means .. should we refer *.py file everytimes even though COMMENT SQL exists but can't use?
DBAs: it's illogical!!!!
Developers: but if we use COMMENT SQL, we customize everytimes to generate migrate files
Developers: it's inefficient!!!!
That's one of the reasons for avoiding ORM.
If you don't mind me asking...
could you give me a feedback to this feature?
https://github.com/django/django/pull/12605
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/62705a74-f16d-42c3-b440-4e3e7628351cn%40googlegroups.com.