Re: Slugs, why would you ever need to store one in the database?

Just one more addition to the replies above: there's a number of snippets[1], recipes and packages[2] which introduce purely autogenerated safe (unique and sometimes also non-ascii-friendly) slugs without using admin. Autopopulated slugs, when used in URLs without exposing internal

Re: Slugs, why would you ever need to store one in the database?

On 23 Jul 2009, at 16:30 , nbv4 wrote: > I'm looking into adding prettier URLs into my site with the help of > slugs. I've never done something like this before, so I'm doing a lot > of reading and am having trouble "getting" slugs. When creating URLs, > couldn't you just do do something like

Re: Slugs, why would you ever need to store one in the database?

On Thu, Jul 23, 2009 at 10:30 AM, nbv4 wrote: > > I'm looking into adding prettier URLs into my site with the help of > slugs. I've never done something like this before, so I'm doing a lot > of reading and am having trouble "getting" slugs. When creating URLs, > couldn't you

Re: Slugs, why would you ever need to store one in the database?

My understanding of the slug field is that prettier URLs are the main point. "Slug" is a newspaper-industry term, and since Django has its roots there, it's now a Django term. Django does' in fact, contain a slugify function:

Slugs, why would you ever need to store one in the database?

I'm looking into adding prettier URLs into my site with the help of slugs. I've never done something like this before, so I'm doing a lot of reading and am having trouble "getting" slugs. When creating URLs, couldn't you just do do something like "example.com/45/slug-goes- here"? Then have the