I appreciate the reply Dennis; some good suggestions. But I was rather hoping that someone would point some "gotcha" (or potentially fatal flaw) with Django that could arise in certain edge cases - especially in connection with a 1:1 design scenario,
On 10 July 2012 19:35, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote: > On Tue, 10 Jul 2012 10:57:21 +0200, Derek <gamesb...@gmail.com> > declaimed the following in gmane.comp.python.django.user: > > > > > DatabaseError at /admin/app/model/1/delete/ > > (1205, 'Lock wait timeout exceeded; try restarting transaction') > > > > Any ideas on how to debug this or see what process or issue is actually > > causing the error? > > > Since it looks like there is an uncommitted transaction floating > around blocking the delete transaction... > > Using something like the old MySQL Administrator control program (I > don't have the newer consolidated Admin/Query program installed) you > might be able to check the "server connections" to see if there is an > open connection (do this check before the time out error occurs) other > than the pending delete (and the administration query for connections > <G>)... Check the MySQL logs... > -- > Wulfraed Dennis Lee Bieber AF6VN > wlfr...@ix.netcom.com HTTP://wlfraed.home.netcom.com/ > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
