Hi, I think (and they were originally, not sure when it got lost), the URLs should be e.g. /person/<id>/<slug> - this has the advantages of the slug, and the advantages of the ID. If there's a name change, it doesn't matter, you can always just redirect to the current canonical URL based upon the ID, no need to remember old slugs. And two things can have the same slug, no yucky "bill-clinton2"s.
ATB, Matthew On 31 Aug 2012, at 19:09, Stephen Booth wrote: > Regarding the slug. Why do you feel it important to have something > readable in the URL? How often do you look at the URL? My view (I'm a > former Database Administrator and designer so this is based on bitter > experience) is that an identifier you can guarentee is unique is more > importtant than a human readable one. This is particular important > where you might have tools not under your direct control inserting and > updating the data (this is also why I always recommend that business > rules should be as close to the data as possible, if they're in the > app layer then you risk another tool/app bypassing them). > > If you DBMS will provide a guarenteed unique key then it would be a > good idea to use it, IME. > > Stephen _______________________________________________ developers-public mailing list [email protected] https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public Unsubscribe: https://secure.mysociety.org/admin/lists/mailman/options/developers-public/archive%40mail-archive.com
