FWIW, I don't see a security issue with exposing a surrogate primary key to the public...
If you're hung up on the issue, though, take Tom's advice and use a slug for each house as an unique key. You might find the street address of a house to be a good slug candidate... On Apr 11, 6:28 pm, ydjango <[EMAIL PROTECTED]> wrote: > I am displaying a list of houses and on clicking on one of the houses > I want to show/edit details > > currently I am using constructing url as /house/edit/123/ > where 123 is house data base primary key for that house. > > Can exposing the primary key in url be any security issue? > > (r'^house/edit/(\d+)/$',editHouse) > > Is there alternative way without exposing the primary key in url? > > Ashish --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
