id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
15508	DetailView view looks for pk or slug by default but the error says id or slug.	John Shimek	nobody	"With the following url rule
{{{
    url(r'^order/(?P<id>\d+)/$', DetailView.as_view(model=Order), name='order-detail')
}}}
Django throws the following error:
{{{
    Generic detail view order must be called with either an object id or a slug.
}}}
From django/django/views/generic/detail.py in get_object, line 45

It confused me for a bit because I am supplying the id of the object. Upon looking at detail.py, it looks for pk and slug. I checked the documentation and found that does mention pk and slug as well, so I am obviously doing it wrong. But, in my mind, id also makes sense. But whether support for id is added or not, I think the error message should be updated to say 'object pk or a slug'. 

I am running 1.3 alpha at the moment, but I checked the method trunk it is the same.


"		closed	Generic views	1.3-alpha		fixed			Accepted	0	0	0	0	0	0