#8623: New comments upgrade guide breaks permalinks, views
---------------------------------+------------------------------------------
Reporter: benspaulding | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version:
Keywords: sql, comments, docs | Stage: Unreviewed
Has_patch: 0 |
---------------------------------+------------------------------------------
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.
--
Ticket URL: <http://code.djangoproject.com/ticket/8623>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
