On Thu, 2007-03-22 at 20:43 +0000, Stephen Newey wrote:
> Hello
>
> I've built a simple photo album with album and photo models. URLs work
> simply using albumslug/photoslug. I'd like to be able to create albums
> within albums, so I've added a self referencing ForeignKey in the
> album model to achieve this.
>
> What I'm trying to work out now is the best approach to creating a
> urlpattern to deal with any number of albums. I could pass
> 'parentslug/childslug' as a string and break it up in my view, but
> that feels messy. I'm sure there's a better way that I'm missing?
You're not missing anything, I don't think. When you think about it, you
have to specify all the components unless you're using some kind of
reversible conversion between the components and a single opaque string
-- and that doesn't lead to very memorable URLs. If you have a URL
structure like /parent/child/grandchild, it's actually fairly nice for
the user, since related URLs are fairly discoverable.
By way of example -- which you may not need, but it won't hurt to have
it in the archives -- in an almost identical situation, I use the
following method to turn a/b/c/d into the tag object 'd' with parent
'c', etc.
def get_by_longname(self, long_name):
"""
Returns the tag with the given long_name.
Raises Tag.DoesNotExist if there is no tag with 'long_name'.
"""
pieces = long_name.strip('/').split('/')
tag = Tag.objects.get(name = pieces[0], parent__isnull = True)
for name in pieces[1:]:
if not name:
# Pruning empty components means that foo//bar will be
# equivalent to foo/bar. Nice to have.
continue
tag = Tag.objects.get(name = name, parent__name__exact = tag.name)
return tag
You write a method like that once and call it wherever you need it.
Doesn't feel messy to me. I realise that's an aesthetic call and I've
been accused of having all the artistic appreciation of a mud puddle,
but I can live with the name calling, since my code is maintainable. By
the way, the above method in my case is a method on a custom manager for
my Tag model, so returning the right Tag object is a matter of calling
Tag.objects.get_by_longname(tag_name)
which also looks pretty natural in code.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
