I posted this note at comp.lang.python and the response there was
that this all works outside of Django. What is the problem with
using MySQL OperationalErrors with Django?
---------
In our database code (we are using django v0.96) we wanted to catch
and handle MySQL OperationalErrors. We use both the Django models and
database connections.
However, even though we confirmed that a
_mysql_exceptions.OperationalError are raised (particularly 1213
deadlock), we cannot catch them with try/except.
Here's the code that did not work:
import _mysql_exceptions
from _mysql_exceptions import OperationalError
try:
database_code()
except (_mysql_exceptions.OperationalError, OperationalError), e:
error_handling()
Originally, we just had one import, but tried both to ensure that was
not the problem. In debugging, we confirmed that both type(e) and
e.__class_ were <class _mysql_exceptions.OperationalError>.
The only work-around we found was:
try:
database_code()
except Exception, e:
if e.__class__.__name__.find('OperationalError') != -1:
error_handling()
else:
raise
This seems silly. If we used any other exception, the except clause
seems to work correctly.
Is there a problem with _mysql_exceptions.OperationalError? Is there
a better work-around?
-----------
Thanks,
Bob
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
