That was it! Thank you very much for your time and effort! On Jan 11, 5:36 pm, Karen Tracey <[email protected]> wrote: > On Mon, Jan 11, 2010 at 4:54 PM, kkerbel <[email protected]> wrote: > > [snip] > > File "/usr/local/lib64/python2.5/site-packages/django/db/models/ > > fields/related.py", line 257, in __get__ > > rel_obj = QuerySet(self.field.rel.to).get(**params) > > > File "/usr/local/lib64/python2.5/site-packages/django/db/models/ > > query.py", line 305, in get > > % self.model._meta.object_name) > > > DoesNotExist: Employee matching query does not exist. > > > [snip] > > > ...also, this only happens with the approval and final_approval > > models...the request model works fine and shows the details with no > > problem. > > You need to check that the Employee in requested_by for ALL Requests is > valid. You already know that the specific Employee associated with the > Request associated with the Approval you are attempting to view is valid > because it is part of what you display on the changelist page. However when > you click on the link to produce the detail page you get an error noting > that an Employee cannot be found. A difference with the detail page, > compared to the changelist page, is that the detail page will have a select > box listing all the Requests the Approval could be associated with. My > guess is somewhere you have a Request linked to an Employee that is no > longer valid. It is that Request which is causing the error. > > Karen
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
