Hi Emily, > > > Since you need that kind of flexibility in which parameters > > and combinations you can have, consider using query string > > parameters instead of url path parameters. > > This is what I would normally have done, but I got the impression that > this kinda went again what django is about, so I was trying to do it in > a more djangoesque way!!
Actually, both ways are djangoesque enough. Normally, you would use the "path style" when your URL's path components are well-defined(/articles/detail/123/, /news/sports/ soccer/, etc.) On the other hand, when you have to drive the main view with a flexible number of parameters some of which may not always be present *and* you need them to appear in many different combinations, the querystring-based pattern fits in better. > Perhaps I will just do it how I would have > before!! > > Thanks for pointing out the obvious (that I had been stupidly > disregarding) to me :) Yeah, sometimes the most obvious solution is also the right one ;) -RD --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
