Monday, January 31, 2011

Re: caching of Models (not the cache middleware)

The behavior seems to have reverted after a couple days. I suspect
that the connection to mysql is being renegotiated, during which it
loses the autocommit setting.

This seems like it should be a setting in django, so if it
renegotiates it will set autocommit again.

Another solution might be to explicitly commit after every select.

On Fri, Jan 28, 2011 at 6:51 PM, Karen Tracey <kmtracey@gmail.com> wrote:
> On Fri, Jan 28, 2011 at 9:45 PM, Brian Craft <bcboy@thecraftstudio.com>
> wrote:
>>
>> Digging into the problem I'm having with a standalone django script,
>> the problem seems to be that django doesn't see updates to the
>> database unless it writes to the database.
>
> Sounds a lot like:
> http://groups.google.com/group/django-users/browse_thread/thread/e25cec400598c06d/
>
> Karen
> --
> http://tracey.org/kmt/
>
> --
> 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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment