Hello there, I confirm that you'll have to adapt get_table_description for each supported backends to introspect column comments.
It seems that introspection support was considered to be a requirement for this ticket[0]. Not sure if that means that the inspectdb logic also needs to be adapted to generate fields with db_comment attached to them. Cheers, Simon Le dimanche 20 juin 2021 à 03:09:55 UTC-4, kimsou...@gmail.com a écrit : > I think about how can I create testcase for DB Comment > > django already has test utility assertion like a "assertTableExists" or > "assertColumnExists" , Index, Constraint .... etc... > > then. I think It seems appropriate that I make new assertion > "assertDBCommentExists" > > but If I make "assertDBCommentExists" , I needs to be modified to contain > db Comment Info to each "DatabaseIntrospection.get_table_description()" > > > I would like to ask for advice on whether this is an appropriate way. > > cc. jchubber > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/dc02b78c-fe79-410c-a3e5-02ac8ea2e980n%40googlegroups.com.
