Hello all,
I'd like some opinions about something. I'd like to know if this is
correct behavior or if it could be considered a bug in django.
This issue is related to 2 models where one model is the superclass of
the other. Let me illustrate with an small abstract example.
class Parent(models.Model):
... (some fields) ...
class Child(Parent):
... (some more fields) ...
In practice I won't do a lot with the Parent model, but since I'm
planning to make a few variations of the Child model, which need a lot
of the same fields and functions, I'd like to define them in the
Parent model and use them in the Child models to avoid the need for
reduntant code. So far so good.
Now I noticed in a view some behavior that I considered a bit
puzzling. The view starts basically like this:
def view(request, some_identifier):
try:
instance = Child.objects.get(some_field=some_identifier)
except Child.DoesNotExist:
... (do something) ...
I noticed that if there wasn't an instance which met the requirements
the DoesNotExist exception didn't get caught by the try: except ...
section. However, if I tried to 'except Parent.DoesNotExist' the
exception was caught.
I feel that the wrong type of exception is being raised, but would
like other people input before deciding to make a ticket.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
