I'm curious why you think view names and arguments will remain unchanged in the future while URLs will not? I understand you can take on the effort needed to guarantee that old view names will still work, but why not take that on for the URLs? Don't you want old bookmarks and search results to continue working in the future also?
--Ned. http://nedbatchelder.com Andrew Ingram wrote: > Hi All, > > I'm trying to to build a model which can store a link to any page on > the site. Ordinarily I'd just use a URLField, but I want to future- > proof it. Instead I'd like to store the view name (including modules) > and the parameter dict. Then I'd like to be able to retrieve these > later and use them to return the correct URL. > > Is there a straightforward way to use django's url parser to take a > URL and return the information I need? Presumably to turn them back > into a URL I just need to use the reverse functionality somehow. > > Regards, > Andrew Ingram > > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
