Well, Django works. :) I'd strongly suggest examining the data at the database layer to see if you are getting the interaction with the database you expect; you might try bringing it up in a test environment and see if you can reproduce it there.
On May 28, 2013, at 1:45 PM, Chris Conover wrote: > No, we are not using the TransactionMiddleware. We are using the following > Django middlewares: CommonMiddleware, SessionMiddleware, MessageMiddleware, > and XFrameOptionsMiddleware. We have a few custom middlewares which handle > stuff for the edge caching. Nothing that produces any writes to MySQL. We are > also using Django Reversion which has a middleware. I'm looking at the > underlying code of that middleware to see if that would cause an issue. The > model that is being saved and submitted to the background task is not under > revision control. > > On Tuesday, May 28, 2013 4:31:08 PM UTC-4, Christophe Pettus wrote: > > On May 28, 2013, at 1:26 PM, Chris Conover wrote: > > > # no middleware that does any writes > > Are you using the Transaction Middleware? > > -- > -- Christophe Pettus > [email protected] > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- Christophe Pettus [email protected] -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
