> > My question is whether Django is a good choice for me. What I'm mostly > worried about is if Django has some sort of a caching mechanisme that is > hard to "turn off", making it vulnerable to not picking up changes to the > data that is done by external processes.
Django does not have anything that's hard to turn off ;) QuerySet instances are indeed cached. See: http://www.djangoproject.com/documentation/db_api/#id3 The keyword here is "instance". What that means to you is that in your views dealing with the display of externally updatable data, you should always create and use a *new instance* of a QuerySet. This will bring in the latest updates from your DB into Django. The Caching Middleware is also capable of caching at various levels. However, that's disabled by default. (http://www.djangoproject.com/documentation/cache/) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
