tickets: 8565
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8565 | 2008-08-26 19:15:31 | 2012-12-16 15:15:49 | 2022-03-06 03:42:35.545120 | Someday/Maybe | closed | contrib.comments | Cleanup/optimization | Normal | dev | wontfix | Comments should use object_id instead of object_pk | `django.contrib.comments.models.BaseCommentAbstractModel` uses `object_pk` to create a generic relation I may be missing something, but straying from the expected and documented default of `object_id` seems to only create extra confusion. I noticed this when trying to add a `GenericTabularInline` | nobody | baumer1122 | comments generic object_pk object_id | 0 | 0 | 0 | 0 | 0 | 0 |