Hello,
I am having little difficulties with django url system and I hope
someone can clear it up. Here's what I want to achieve: we're going to
have a tree-based catalog in our app and we'd like to index it like
this: name1/name2/name3/... I've created a database lookup table url <-
> id with urls being automatically generated at catalog save time. Now
I would like to plug this in django url resolving process (first I put
in view to which I passed whole path, but that is simply wrong for a
couple of reasons). Also, I don't want to completely replace
RegexURLResolver, because other parts of our site will be using it. So
what I'd like would probably be some refactoring of the resolvers. For
the time being I subclassed RegexURLPattern and implemented custom
resolve method -- it is hacky, but works straight away when I put my
subclass in url_patterns. The problem is, there seems to be no easy
way, to make reverse work. I was thinking about all of it a lot, also
googling a lot and I found no answers. So I wonder: what's the best
way to make database URL resolving play nicely with the default regex
resolving? Is there any way at all?

With regards,
Marek Bernat

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to