Hallöchen!
Malcolm Tredinnick writes:
> On Wed, 2008-11-19 at 10:21 +0900, Ian Lewis wrote:
>
>> I've run into the following error in a SQL DB envornment and was
>> wondering if any one else had run into problems with Deadlocking
>> with MySQL. What would be the proper way to handle this kind of
The application I'm referring to uses CherryPy without any ORM. We
have a shortcut "execute" method that all DB calls go through. We just
added special exception handling to that call. Not sure how you would
do the same thing in Django. You'd probably have to dig into django.db
to see if you can w
This isn't something that happens regularly. This error has only come
about once as far as I can tell. It just isn't properly handled and I
wondered what other folks did. Ideally we would have something like
you described that retrys the writes but it occurs infrequenly enough
that I think we can
Unrelated to Django, but we occasionally get deadlocks in MySQL due to
separate tasks running at the same time and accessing some tables in
common. We recently added logic to catch the exception, wait a second
or two, and retry it a few times before we give up. Most of the time,
that fixes it.
I
On Wed, 2008-11-19 at 10:21 +0900, Ian Lewis wrote:
> I've run into the following error in a SQL DB envornment and was
> wondering if any one else had run into problems with Deadlocking with
> MySQL. What would be the proper way to handle this kind of error in
> Django?
>
> Do most folks simply
I've run into the following error in a SQL DB envornment and was
wondering if any one else had run into problems with Deadlocking with
MySQL. What would be the proper way to handle this kind of error in
Django?
Do most folks simply catch the OperationalError and show some sort of
error to the use
6 matches
Mail list logo
