tickets: 8623
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8623 | 2008-08-27 21:25:48 | 2008-09-10 04:16:40 | 2022-03-06 03:42:44.608334 | Design decision needed | closed | contrib.comments | wontfix | New comments upgrade guide breaks permalinks, views | The SQL provided by the [http://docs.djangoproject.com/en/dev/ref/contrib/comments/upgrade/#upgrading-data comment upgrade guide] does not preserve a comment’s {{{id}}} and therefore breaks most permalinks and any detail view that uses the {{{id}}} to resolve the url. Neither of these cases are absolutely critical because: 1. permalinks using {{{<url>/#<comment_id>}}} still get you to the page, just not the comment, 2. almost no one (I would guess) uses a comment detail view. Further, if someone was using ''both'' comments and free comments it will not be possible to preserve the {{{id}}}’s for both as they are being merged in to one table. But they could choose which one to preserve and do that one first. Unfortunately my SQL-fu is not good enough to write a patch, or even know if preserving the comment’s {{{id}}} is possible. | nobody | benspaulding | sql, comments, docs | 0 | 0 | 0 | 0 | 0 | 0 |