> David: The slugs wouldn't be overlapping if they inherited from some > sort of "Organization" model with unique slug. The user could also add > validation code to prevent company and schools having same slugs.
If you have a common base model this sounds like some polymorphic model problem, which does not need to be solved in the URLs (and probably should not). There are existing third party solutions, which may help you get the right model back, when fetching one "Organization". An user validation is only useful if you put the logic into an unrelated app, as my proposed alias app. Otherwise you will need to mix your models, at least when doing validation. This may not follow the loose coupling philosophy (https://docs.djangoproject.com/en/dev/misc/design-philosophies/) of Django. If you have this app the name resolution can be done without doing fallbacks anywhere in your code. Anyways, about your proposal: This is somethign that does not need to be inside Django core. So why not just start an thirt party app implementing the proposal? David -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
