On 5/8/07, Brandon Low <[EMAIL PROTECTED]> wrote: > > Still not sure what's going on myself -- I've had one more occurence of > the error, and have now confirmed that autocommit is on in the > production application (by printing the result of select @@autocommit). > > It sounds quite possible that it's the immediate foreign key constraint > check that's causing the problem, this would be fixed if I upgraded to > 5.1? Any other work arounds you can suggest?
5.1 looks to be the same in this respect, but if autocommit is on somehow, then that's the most likely problem. I vaguely remember that if you are using auto-reconnect (particularly if you use connection.ping(True)) that autocommit is not automatically turned off; the initial setting is controlled by option files, so check your server default. However, I don't think that's the problem here. -- Patriotism means to stand by the country. It does not mean to stand by the president. -- T. Roosevelt This message has been scanned for memes and dangerous content by MindScanner, and is believed to be unclean. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
